How to integrate Mailcoach MCP with Google ADK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Mailcoach Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting Mailcoach to Google ADK 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 Google ADK 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 a Mailcoach account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Mailcoach
  • Build an agent that connects to Mailcoach through MCP
  • Interact with Mailcoach using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio-google python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Mailcoach via MCP
  • composio-google provides the Google ADK provider
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
print("Initializing Composio client...")
composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

print("Creating Composio session...")
composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["mailcoach"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url
print(f"Composio MCP HTTP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
print("Creating Composio toolset for the agent...")
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )
)

root_agent = Agent(
    model="gemini-2.5-pro",
    name="composio_agent",
    description="An agent that uses Mailcoach tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Mailcoach operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web
Execute the agent from the project root. The web command opens a web portal where you can chat with the agent. What's happening:
  • adk run runs the agent in CLI mode
  • adk web opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Mailcoach and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

def main():
    try:
        load_dotenv()

        warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

        GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
        COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
        COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

        if not GOOGLE_API_KEY:
            raise ValueError("GOOGLE_API_KEY is not set in the environment.")
        if not COMPOSIO_API_KEY:
            raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
        if not COMPOSIO_USER_ID:
            raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

        print("Initializing Composio client...")
        composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

        print("Creating Composio session...")
        composio_session = composio_client.create(
            user_id=COMPOSIO_USER_ID,
            toolkits=["mailcoach"],
        )

        COMPOSIO_MCP_URL = composio_session.mcp.url
        print(f"Composio MCP HTTP URL: {COMPOSIO_MCP_URL}")

        print("Creating Composio toolset for the agent...")
        composio_toolset = McpToolset(
            connection_params=StreamableHTTPConnectionParams(
                url=COMPOSIO_MCP_URL,
                headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
            )
        )

        root_agent = Agent(
            model="gemini-2.5-pro",
            name="composio_agent",
            description="An agent that uses Mailcoach tools to perform actions.",
            instruction=(
                "You are a helpful assistant connected to Composio. "
                "You have the following tools available: "
                "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
                "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
                "Use these tools to help users with Mailcoach operations."
            ),
            tools=[composio_toolset],
        )

        print("\nAgent setup complete. You can now run this agent directly ;)")

    except Exception as e:
        print(f"\nAn error occurred during agent setup: {e}")

if __name__ == "__main__":
    main()

Conclusion

You've successfully integrated Mailcoach with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Mailcoach using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Mailcoach tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

How to build Mailcoach MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Mailcoach MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Mailcoach MCP with Claude Agent SDK

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 Google ADK?

Yes, you can. Google ADK 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