How to integrate Mailcoach MCP with Claude Agent SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Mailcoach Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Mailcoach to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Mailcoach agent that can create a new email campaign for product launch, add a subscriber to the weekly newsletter list, tag all subscribers interested in webinars, confirm a subscriber's double opt-in registration through natural language commands.

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

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

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 Mailcoach
  • Configure an AI agent that can use Mailcoach as a tool
  • Run a live chat session where you can ask the agent to perform Mailcoach 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 Mailcoach MCP server, and what's possible with it?

The Mailcoach MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mailcoach account. It provides structured and secure access to your email marketing platform, so your agent can manage campaigns, organize subscriber lists, create templates, and automate email workflows on your behalf.

  • Email campaign creation and scheduling: Direct your agent to launch new campaigns, send emails to specific lists, or set up campaign schedules based on your marketing needs.
  • Subscriber list and segmentation management: Let your agent create new email lists, add or confirm subscribers, and apply tags for better audience segmentation and targeting.
  • Template management and customization: Instruct your agent to create, update, or organize reusable email templates and transactional templates for efficient campaign building.
  • Automated suppression and bounce handling: Have your agent add suppressions for bounced or blocked addresses, keeping your lists clean and compliant with deliverability best practices.
  • Bulk subscriber import and data enrichment: Enable your agent to import subscribers via CSV, append new data to existing imports, and streamline growth of your contact lists.

Supported Tools & Triggers

Tools
Add Mailcoach CampaignTool to create a new mailcoach campaign.
Add Email ListTool to create a new email list.
Add suppressionTool to add a suppression entry.
Add Tag to Email ListTool to create a new tag within a specific email list.
Add Tags to SubscriberTool to add tags to a subscriber.
Add TemplateTool to create a new email template.
Add Transactional Email TemplateTool to create a new template that can be used for transactional emails.
Append to Subscriber ImportTool to append csv data to an existing subscriber import.
Confirm SubscriberTool to confirm a subscriber’s subscription.
Create Subscriber ImportTool to create a new subscriber import.
Delete CampaignTool to delete a campaign by uuid.
Delete Email ListTool to delete an email list by uuid.
Delete SendTool to delete a sent item by its uuid.
Delete SubscriberTool to delete a subscriber by uuid.
Delete Subscriber ImportTool to delete a subscriber import by its uuid.
Delete SuppressionTool to delete a suppression entry by uuid.
Delete Tag from Email ListTool to delete a tag from an email list.
Delete TemplateTool to delete a template by uuid.
Delete Transactional MailTool to delete a transactional mail by its uuid.
Get All CampaignsTool to retrieve all campaigns.
Get All Sent ItemsTool to retrieve all sent items.
Get All Subscriber ImportsTool to retrieve all subscriber imports.
Get All SuppressionsTool to list all suppression entries.
Get All TagsTool to retrieve all tags for a specific email list.
Get All TemplatesTool to retrieve all templates.
Get All Transactional Email TemplatesTool to retrieve all transactional email templates.
Get Email ListsTool to retrieve all email lists.
Get Specific CampaignTool to retrieve details of a specific mailcoach campaign.
Get Specific Email ListTool to retrieve a specific email list.
Get Specific SubscriberTool to retrieve a specific subscriber.
Get Specific SuppressionTool to retrieve a specific suppression entry.
Get Specific TagTool to retrieve details of a specific tag.
Get Specific TemplateTool to retrieve details of a specific template.
Get Transactional MailsTool to retrieve all transactional mail templates.
Remove Tags from SubscriberTool to remove tags from a subscriber.
Resend Subscriber ConfirmationTool to resend confirmation email to a subscriber.
Start Subscriber ImportTool to start processing a subscriber import.
Subscribe To Email ListTool to add or update a subscriber in an email list.
Unsubscribe SubscriberTool to unsubscribe a subscriber from an email list.
Update CampaignTool to update an existing mailcoach campaign.
Update Email ListTool to update an existing email list.
Update SubscriberTool to update a subscriber.
Update Subscriber ImportTool to update an existing subscriber import.
Update TagTool to update an existing tag within an email list.
Update TemplateTool to update an existing template's name or content.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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 Mailcoach 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 Mailcoach 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 Mailcoach
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["mailcoach"]
    )

    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 Mailcoach
  • 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 Mailcoach 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 Mailcoach
  • 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 Mailcoach 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 Mailcoach
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["mailcoach"]
    )

    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 Mailcoach 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 Mailcoach 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 Mailcoach MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Mailcoach MCP with OpenAI Agents SDK

Google ADK

Google ADK

Use Mailcoach MCP with Google ADK

LangChain

LangChain

Use Mailcoach MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Mailcoach MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Mailcoach MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Mailcoach MCP with LlamaIndex

CrewAI

CrewAI

Use Mailcoach MCP with CrewAI

FAQ

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

With a standalone Mailcoach MCP server, the agents and LLMs can only access a fixed set of Mailcoach tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Mailcoach 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 Mailcoach tools.

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

Yes, absolutely. You can configure which Mailcoach 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 Mailcoach data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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.

Book a call↗Get started for free