How to integrate Enginemailer MCP with Mastra AI

This guide walks you through connecting Enginemailer to Mastra AI 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 Mastra AI 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 free Get a demo

Enginemailer

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

Managed auth

Connect Enginemailer without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

This guide will help you understand how to give your Mastra AI 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 SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Set up your environment so Mastra, OpenAI, and Composio work together
Create a Tool Router session in Composio that exposes Enginemailer tools
Connect Mastra's MCP client to the Composio generated MCP URL
Fetch Enginemailer tool definitions and attach them as a toolset
Build a Mastra agent that can reason, call tools, and return structured results
Run an interactive CLI where you can chat with your Enginemailer agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

MCP Client: Built-in support for Model Context Protocol servers
Toolsets: Organize tools into logical groups
Step Callbacks: Monitor and debug agent execution
OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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:

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

Step-by-step Guide

Step by step09 STEPS

Prerequisites

Before starting, make sure you have:

Node.js 18 or higher
A Composio account with an active API key
An OpenAI API key
Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key.
You need credits or a connected billing setup to use the models.
Store the key somewhere safe.

Composio API Key

Log in to the Composio dashboard.
Go to Settings and copy your API key.
This key lets your Mastra agent talk to Composio and reach Enginemailer through MCP.

Install dependencies

bash

npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

@composio/core is the Composio SDK for creating MCP sessions
@mastra/core provides the Agent class
@mastra/mcp is Mastra's MCP client
@ai-sdk/openai is the model wrapper for OpenAI
dotenv loads environment variables from .env

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates your requests to Composio
COMPOSIO_USER_ID tells Composio which user this session belongs to
OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});

What's happening:

dotenv/config auto loads your .env so process.env.* is available
openai gives you a Mastra compatible model wrapper
Agent is the Mastra agent that will call tools and produce answers
MCPClient connects Mastra to your Composio MCP server
Composio is used to create a Tool Router session

Create a Tool Router session for Enginemailer

typescript

async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["enginemailer"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Enginemailer MCP URL:", composioMCPUrl);

What's happening:

create spins up a short-lived MCP HTTP endpoint for this user
The toolkits array contains "enginemailer" for Enginemailer access
session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript

const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);

What's happening:

MCPClient takes an id for this client and a list of MCP servers
The headers property includes the x-api-key for authentication
getTools fetches the tool definitions exposed by the Enginemailer toolkit

Create the Mastra agent

typescript

const agent = new Agent({
    name: "enginemailer-mastra-agent",
    instructions: "You are an AI agent with Enginemailer tools via Composio.",
    model: "openai/gpt-5",
  });

What's happening:

Agent is the core Mastra agent
name is just an identifier for logging and debugging
instructions guide the agent to use tools instead of only answering in natural language
model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript

let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        enginemailer: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

What's happening:

messages keeps the full conversation history in Mastra's expected format
agent.generate runs the agent with conversation history and Enginemailer toolsets
maxSteps limits how many tool calls the agent can take in a single run
onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Enginemailer and Mastra AI:

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["enginemailer"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      enginemailer: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "enginemailer-mastra-agent",
    instructions: "You are an AI agent with Enginemailer tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { enginemailer: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Enginemailer through Composio's Tool Router. You can extend this further by:

Adding other toolkits like Gmail, Slack, or GitHub
Building a web-based chat interface around this agent
Using multiple MCP endpoints to enable cross-app workflows

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

Use Enginemailer MCP with OpenAI Agents SDK

Claude Agent SDK

Use Enginemailer MCP with Claude Agent SDK

Claude Code

Use Enginemailer MCP with Claude Code

Claude Cowork

Use Enginemailer MCP with Claude Cowork

Codex

Use Enginemailer MCP with Codex

OpenClaw

Use Enginemailer MCP with OpenClaw

Hermes

Use Enginemailer MCP with Hermes

CLI

Use Enginemailer MCP with CLI

Google ADK

Use Enginemailer MCP with Google ADK

LangChain

Use Enginemailer MCP with LangChain

Vercel AI SDK

Use Enginemailer MCP with Vercel AI SDK

LlamaIndex

Use Enginemailer MCP with LlamaIndex

CrewAI

Use Enginemailer MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Oauth2

Reddit is a social news platform with thriving user-driven communities (subreddits). It's the go-to place for discussion, content sharing, and viral marketing.

Facebook

Oauth2

Facebook is a social media and advertising platform for businesses and creators. It helps you connect, share, and manage content across your public Facebook Pages.

Oauth2

LinkedIn is a professional networking platform for connecting, sharing content, and engaging with business opportunities. It's the go-to place for building your professional brand and unlocking new career connections.

Active campaign

Api Key

ActiveCampaign is a marketing automation and CRM platform for managing email campaigns, sales pipelines, and customer segmentation. It helps businesses engage customers and drive growth through smart automation and targeted outreach.

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. Mastra AI 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 FREE BOOK A DEMO

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

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

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

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

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

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

Co-Founder, Ingram Technologies

How to integrate Enginemailer MCP with Mastra AI

Connect Enginemailer without auth hassles

Introduction

Also integrate Enginemailer with

TL;DR

What is Mastra AI?

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

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import libraries and validate environment

Create a Tool Router session for Enginemailer

Configure Mastra MCP client and fetch tools

Create the Mastra agent

Set up interactive chat interface

Complete Code

Conclusion

Supported Tools

How to build Enginemailer MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

LlamaIndex

CrewAI

Explore Other Toolkits

Reddit

Facebook

Linkedin

Active campaign

Frequently asked questions

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

Can I use Tool Router MCP with Mastra AI?+

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

How safe is my data with Composio Tool Router?+

Start with Enginemailer.It takes 30 seconds.

Teams ship real agents on Composio