How to integrate Enginemailer MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Enginemailer logo
Claude Agent SDK logo
divider

Introduction

This guide walks you through connecting Enginemailer to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Enginemailer agent that can add new subscriber to newsletter list, pause tomorrow's scheduled marketing campaign, export email delivery report from last week through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Enginemailer account through Composio's Enginemailer MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Enginemailer with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Enginemailer
  • Configure an AI agent that can use Enginemailer as a tool
  • Run a live chat session where you can ask the agent to perform Enginemailer operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Enginemailer MCP server, and what's possible with it?

The Enginemailer MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Enginemailer account. It provides structured and secure access to your email marketing platform, so your agent can perform actions like creating campaigns, managing subscriber lists, exporting reports, and sending personalized email campaigns on your behalf.

  • Campaign creation and scheduling: Direct your agent to set up new email campaigns, configure content, and schedule delivery to your audience.
  • Subscriber management: Have your agent add new subscribers to your lists, including custom fields and segmentation for targeted outreach.
  • Instant campaign delivery and controls: Command your agent to send campaigns immediately or pause scheduled campaigns for last-minute adjustments.
  • Campaign monitoring and reporting: Let your agent export detailed email campaign reports as CSV files and check the status of ongoing exports.
  • Audience segmentation and subcategory retrieval: Guide your agent to fetch subcategories and organize recipients for more personalized and effective campaigns.

Supported Tools & Triggers

Tools
Activate SubscriberTool to activate an inactive subscriber in EngineMailer.
Add or Update SubscriberTool to add or update a subscriber with custom fields via N8N integration.
Check Batch Update StatusTool to check the status of a batch subscriber update operation.
Batch Update SubscribersTool to add or update multiple subscribers with custom fields in a single batch operation.
Check Export Status V2Tool to check status of a previously requested CSV report export.
Test API ConnectionTool to test API connection and verify authentication.
Create CampaignTool to create a new email campaign.
Delete CampaignTool to delete an undelivered email campaign.
Delete Recipient ListTool to delete an existing recipient list from a targeted campaign.
Delete SubscriberTool to remove a subscriber from the system by email address.
Export CSV Report V2Tool to export a transactional email report as CSV.
Find SubscriberTool to find a subscriber by email address via N8N integration.
Get Custom Field ListTool to retrieve the list of custom fields configured for subscribers.
Get List CampaignTool to get a list of undelivered campaigns.
Get New SubscribersTool to retrieve new subscribers with optional filtering by source, form, page, or popup.
Get SubcategoriesTool to retrieve subcategories for a given category.
Get SubscriberTool to retrieve subscriber information by email address.
Get Subscriber Autoresponder CompletedTool to retrieve subscribers who completed autoresponders with optional filtering by autoresponder ID.
Get Subscriber Autoresponder TriggeredTool to retrieve subscribers who triggered autoresponders with optional filtering by autoresponder ID.
Get Deleted SubscribersTool to retrieve deleted subscribers since last polling date.
Get Subscribers ModifiedTool to retrieve modified subscribers since last polling date with optional limit.
Get Subscribers TaggedTool to retrieve subscribers who were tagged with optional filtering by subcategory.
Get Untagged SubscribersTool to retrieve subscribers who were untagged from subcategories.
Get Unsubscribe EventsTool to retrieve unsubscribe events with optional filtering by campaign or autoresponder.
Insert SubscriberTool to add a new subscriber with optional custom fields.
List AutorespondersTool to retrieve a list of all autoresponders.
List CampaignsTool to retrieve a list of all campaigns.
List FormsTool to retrieve a list of available forms in Enginemailer.
List PagesTool to retrieve a list of all pages.
List PopupsTool to retrieve a list of popups from Enginemailer.
List TemplatesTool to retrieve a list of all email templates.
Pause CampaignTool to pause a scheduled email campaign.
Create/Update CategoryTool to create or update a category for subscriber segmentation.
Update SubscriberTool to update data for an existing subscriber in EngineMailer.
Send CampaignTool to send an email campaign immediately.
Tag Subscriber to SubcategoryTool to tag a subscriber to a specific subcategory via N8N API endpoint.
Unsubscribe (N8N)Tool to unsubscribe a subscriber via N8N API endpoint.
Unsubscribe SubscriberTool to unsubscribe a subscriber from the email list.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Enginemailer account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Enginemailer functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Enginemailer
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["enginemailer"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Enginemailer
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Enginemailer tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Enginemailer
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Enginemailer and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Enginemailer
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["enginemailer"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Enginemailer tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Enginemailer through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Enginemailer MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Enginemailer MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Enginemailer MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Enginemailer MCP with Claude Cowork

Codex logo

Codex

Use Enginemailer MCP with Codex

OpenClaw logo

OpenClaw

Use Enginemailer MCP with OpenClaw

Hermes logo

Hermes

Use Enginemailer MCP with Hermes

CLI logo

CLI

Use Enginemailer MCP with CLI

Google ADK logo

Google ADK

Use Enginemailer MCP with Google ADK

LangChain logo

LangChain

Use Enginemailer MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Enginemailer MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Enginemailer MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Enginemailer MCP with LlamaIndex

CrewAI logo

CrewAI

Use Enginemailer MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Enginemailer MCP?

With a standalone Enginemailer MCP server, the agents and LLMs can only access a fixed set of Enginemailer tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Enginemailer and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Enginemailer tools.

Can I manage the permissions and scopes for Enginemailer while using Tool Router?

Yes, absolutely. You can configure which Enginemailer scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Enginemailer data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗