How to integrate Enginemailer MCP with Google ADK

This guide walks you through connecting Enginemailer to Google ADK 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 Google ADK 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.

Get started for freeGet a demo
Enginemailer logoEnginemailer
Api Key

Enginemailer is an email marketing platform for managing contacts, campaigns, and sending personalized emails. It helps businesses automate outreach and boost engagement with targeted messaging.

38 Tools

Introduction

This guide walks you through connecting Enginemailer to Google ADK 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 Google ADK 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

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLILangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get a Enginemailer account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Enginemailer
  • Build an agent that connects to Enginemailer through MCP
  • Interact with Enginemailer 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 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.

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

Step by step09 STEPS
1

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
2

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.
3

Install dependencies

bash
pip install google-adk composio 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 Enginemailer via MCP
  • python-dotenv loads environment variables
4

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
5

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
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
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
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["enginemailer"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP 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
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio 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 Enginemailer 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
9

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 Enginemailer 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

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.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["enginemailer"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio 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 Enginemailer operations."
    ),  
    tools=[composio_toolset],
)

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Enginemailer 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.

TOOLS

Supported Tools

Every Enginemailer action and event your agent gets out of the box.

Activate Subscriber

Tool to activate an inactive subscriber in EngineMailer.

Add or Update Subscriber

Tool to add or update a subscriber with custom fields via N8N integration.

Check Batch Update Status

Tool to check the status of a batch subscriber update operation.

Batch Update Subscribers

Tool to add or update multiple subscribers with custom fields in a single batch operation.

Check Export Status V2

Tool to check status of a previously requested CSV report export.

Test API Connection

Tool to test API connection and verify authentication.

Create Campaign

Tool to create a new email campaign.

Delete Campaign

Tool to delete an undelivered email campaign.

Delete Recipient List

Tool to delete an existing recipient list from a targeted campaign.

Delete Subscriber

Tool to remove a subscriber from the system by email address.

Export CSV Report V2

Tool to export a transactional email report as CSV.

Find Subscriber

Tool to find a subscriber by email address via N8N integration.

Get Custom Field List

Tool to retrieve the list of custom fields configured for subscribers.

Get List Campaign

Tool to get a list of undelivered campaigns.

Get New Subscribers

Tool to retrieve new subscribers with optional filtering by source, form, page, or popup.

Get Subcategories

Tool to retrieve subcategories for a given category.

Get Subscriber

Tool to retrieve subscriber information by email address.

Get Subscriber Autoresponder Completed

Tool to retrieve subscribers who completed autoresponders with optional filtering by autoresponder ID.

Get Subscriber Autoresponder Triggered

Tool to retrieve subscribers who triggered autoresponders with optional filtering by autoresponder ID.

Get Deleted Subscribers

Tool to retrieve deleted subscribers since last polling date.

Get Subscribers Modified

Tool to retrieve modified subscribers since last polling date with optional limit.

Get Subscribers Tagged

Tool to retrieve subscribers who were tagged with optional filtering by subcategory.

Get Untagged Subscribers

Tool to retrieve subscribers who were untagged from subcategories.

Get Unsubscribe Events

Tool to retrieve unsubscribe events with optional filtering by campaign or autoresponder.

Insert Subscriber

Tool to add a new subscriber with optional custom fields.

List Autoresponders

Tool to retrieve a list of all autoresponders.

List Campaigns

Tool to retrieve a list of all campaigns.

List Forms

Tool to retrieve a list of available forms in Enginemailer.

List Pages

Tool to retrieve a list of all pages.

List Popups

Tool to retrieve a list of popups from Enginemailer.

List Templates

Tool to retrieve a list of all email templates.

Pause Campaign

Tool to pause a scheduled email campaign.

Create/Update Category

Tool to create or update a category for subscriber segmentation.

Update Subscriber

Tool to update data for an existing subscriber in EngineMailer.

Send Campaign

Tool to send an email campaign immediately.

Tag Subscriber to Subcategory

Tool to tag a subscriber to a specific subcategory via N8N API endpoint.

Unsubscribe (N8N)

Tool to unsubscribe a subscriber via N8N API endpoint.

Unsubscribe Subscriber

Tool to unsubscribe a subscriber from the email list.

FRAMEWORKS

How to build Enginemailer MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Enginemailer MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Enginemailer MCP with Claude Agent 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

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

Frequently asked questions

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.

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 Enginemailer tools.

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.

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.

Start with Enginemailer.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Enginemailer tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies