# How to integrate Emelia MCP with Mastra AI

```json
{
  "title": "How to integrate Emelia MCP with Mastra AI",
  "toolkit": "Emelia",
  "toolkit_slug": "emelia",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/emelia/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/emelia/framework/mastra-ai.md",
  "updated_at": "2026-05-12T10:10:18.624Z"
}
```

## Introduction

This guide walks you through connecting Emelia to Mastra AI using the Composio tool router. By the end, you'll have a working Emelia agent that can find email address for john doe at acme corp, add jane.smith@email.com to new leads campaign, remove bob.jones@company.com from q2 outreach campaign through natural language commands.
This guide will help you understand how to give your Mastra AI agent real control over a Emelia account through Composio's Emelia MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Emelia with

- [OpenAI Agents SDK](https://composio.dev/toolkits/emelia/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/emelia/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/emelia/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/emelia/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/emelia/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/emelia/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/emelia/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/emelia/framework/cli)
- [Google ADK](https://composio.dev/toolkits/emelia/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/emelia/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/emelia/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/emelia/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/emelia/framework/crew-ai)

## 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 Emelia tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Emelia 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 Emelia 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 Emelia MCP server, and what's possible with it?

The Emelia MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Emelia account. It provides structured and secure access to your B2B outreach operations, so your agent can perform actions like launching campaigns, managing contacts, finding prospect emails, and tracking outreach activities on your behalf.
- Automated campaign creation and management: Instruct your agent to create new email or LinkedIn campaigns, add contacts, or remove contacts from campaigns to keep your outreach efforts streamlined and organized.
- Prospect email discovery: Have your agent find verified email addresses for specific contacts using full name and company details, accelerating your lead generation process.
- Contact blacklisting and compliance: Direct your agent to add contacts to the blacklist, ensuring that no further emails are sent and helping you stay compliant with outreach best practices.
- Real-time campaign activity tracking: Retrieve detailed campaign activities and create webhooks to monitor engagement, so you’re always up to date on your outreach performance.
- Webhook automation for event-driven workflows: Let your agent create or delete webhooks to automate follow-ups and synchronize campaign updates across your sales stack.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `EMELIA_ADD_CONTACT_TO_BLACKLIST` | Add Contact to Blacklist | Tool to add a contact to the email blacklist. Use after confirming that no further emails should be sent to a specific address. Example: 'Add blocked_user@example.com to blacklist.' |
| `EMELIA_ADD_CONTACT_TO_CAMPAIGN` | Add Contact To Campaign | Tool to add a contact to an email campaign. Use when you have collected subscriber details and want to enroll them in a campaign. |
| `EMELIA_CREATE_CAMPAIGN` | Create Campaign | Tool to create a new email campaign. Use after you have finalized the campaign name. |
| `EMELIA_CREATE_LINKEDIN_CAMPAIGN` | Create LinkedIn Campaign | Tool to create a new LinkedIn campaign. Use when you need to launch a LinkedIn outreach sequence. |
| `EMELIA_CREATE_WEBHOOK` | Create Webhook | Tool to create a new webhook for campaign events. Use when you need to subscribe to activity updates after determining the campaign ID and desired events. |
| `EMELIA_DELETE_CONTACT_FROM_CAMPAIGN` | Delete Contact From Campaign | Tool to remove a contact from an email campaign. Use when you need to revoke a contact's subscription from a specific campaign. Note: this operation is irreversible. |
| `EMELIA_DELETE_CONTACT_FROM_LINKEDIN_CAMPAIGN` | Delete Contact From LinkedIn Campaign | Tool to delete a contact from a LinkedIn campaign. Use when you need to remove a contact by campaign ID and contact URL. Call after confirming the contact exists in the campaign. |
| `EMELIA_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a specific webhook. Use when you need to remove an existing webhook by URL after identifying the campaign. |
| `EMELIA_FIND_EMAIL_SINGLE_CONTACT` | Find Email of Single Contact | Tool to initiate a job to find the email address of a specific contact. Use when you have the contact's full name and company details and want to retrieve their email address. |
| `EMELIA_GET_CAMPAIGN_ACTIVITIES` | Get Campaign Activities | Tool to retrieve activities for a specific email campaign. Use after obtaining the campaign ID. |
| `EMELIA_GET_FIND_EMAIL_RESULT` | Get Find Email Result | Tool to retrieve the result of a previously initiated email find job. Use after initiating a find-email job to check its status and outcome. |
| `EMELIA_GET_FIND_PHONE_RESULT` | Get Find Phone Result | Tool to retrieve the outcome of a previously initiated phone-find job. Use after starting a job to fetch its status and details by job ID. |
| `EMELIA_GET_LINKEDIN_CAMPAIGN_ACTIVITIES` | Get Campaign Activities | Tool to retrieve activities for a campaign. Use when you need to inspect engagement events for a specific campaign. |
| `EMELIA_GET_VERIFY_EMAIL_RESULT` | Get Verify Email Result | Tool to get the result of an email verification job. Use after initiating an email verification job to check its status and outcome. |
| `EMELIA_INITIATE_EMAIL_VERIFICATION_JOB` | Initiate Email Verification Job | Tool to initiate an asynchronous email verification job." |
| `EMELIA_INITIATE_PHONE_FIND_JOB` | Initiate Phone Find Job | Tool to initiate a phone-find job for a single contact. Use when you want to retrieve a contact's phone number based on their email address. |
| `EMELIA_LIST_CAMPAIGN_CONTACTS` | List Campaign Contacts | Tool to list contacts in a specific email campaign. Use when you need to retrieve campaign subscribers with optional pagination. |
| `EMELIA_LIST_CAMPAIGNS` | List Campaigns | Tool to retrieve all email campaigns. Use when you need to fetch the list of campaigns, with optional pagination or search filters. |
| `EMELIA_LIST_EMAIL_PROVIDERS` | List Email Providers | Tool to retrieve all configured email providers. Use after setting up your email providers to view them. |
| `EMELIA_LIST_LINKEDIN_CAMPAIGNS` | List LinkedIn Campaigns | Tool to list all LinkedIn campaigns. Use when you need an overview of your LinkedIn campaigns and want to paginate results. |
| `EMELIA_LIST_WEBHOOKS` | List webhooks | Tool to retrieve all webhooks. Use when you need to fetch every configured webhook in Emelia. |
| `EMELIA_REMOVE_CONTACT_FROM_BLACKLIST` | Remove Contact from Blacklist | Tool to remove a contact or domain from the email blacklist. Use after verifying that the address or domain should no longer be blocked. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Emelia MCP server is an implementation of the Model Context Protocol that connects your AI agent to Emelia. It provides structured and secure access so your agent can perform Emelia operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. 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

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.
- This key lets your Mastra agent talk to Composio and reach Emelia through MCP.

### 2. Install dependencies

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
```bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv
```

### 3. Set up environment variables

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
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import libraries and validate environment

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
```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,
});
```

### 5. Create a Tool Router session for Emelia

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "emelia" for Emelia access
- session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
```typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["emelia"],
    },
  );

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

### 6. Configure Mastra MCP client and fetch tools

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 Emelia toolkit
```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);
```

### 7. Create the Mastra agent

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
```typescript
const agent = new Agent({
    name: "emelia-mastra-agent",
    instructions: "You are an AI agent with Emelia tools via Composio.",
    model: "openai/gpt-5",
  });
```

### 8. Set up interactive chat interface

What's happening:
- messages keeps the full conversation history in Mastra's expected format
- agent.generate runs the agent with conversation history and Emelia 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
```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: {
        emelia: 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);
});
```

## Complete Code

```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: ["emelia"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "emelia-mastra-agent",
    instructions: "You are an AI agent with Emelia 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: { emelia: 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 Emelia 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

## How to build Emelia MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/emelia/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/emelia/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/emelia/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/emelia/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/emelia/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/emelia/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/emelia/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/emelia/framework/cli)
- [Google ADK](https://composio.dev/toolkits/emelia/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/emelia/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/emelia/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/emelia/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/emelia/framework/crew-ai)

## Related Toolkits

- [Aeroleads](https://composio.dev/toolkits/aeroleads) - Aeroleads is a B2B lead generation platform for finding business emails and phone numbers. Grow your sales pipeline faster with powerful prospecting tools.
- [Autobound](https://composio.dev/toolkits/autobound) - Autobound is an AI-powered sales engagement platform that crafts hyper-personalized outreach and insights. It helps sales teams boost response rates and close more deals through tailored content and recommendations.
- [Better proposals](https://composio.dev/toolkits/better_proposals) - Better Proposals is a web-based tool for crafting and sending professional proposals. It helps teams impress clients and close deals faster with slick, easy-to-use templates.
- [Bidsketch](https://composio.dev/toolkits/bidsketch) - Bidsketch is a proposal software that helps businesses create professional proposals quickly and efficiently. It streamlines the proposal process, saving time while boosting client win rates.
- [Bolna](https://composio.dev/toolkits/bolna) - Bolna is an AI platform for building conversational voice agents. It helps businesses automate support and streamline interactions through natural, voice-powered conversations.
- [Botsonic](https://composio.dev/toolkits/botsonic) - Botsonic is a no-code AI chatbot builder for easily creating and deploying chatbots to your website. It empowers businesses to offer conversational experiences without writing code.
- [Botstar](https://composio.dev/toolkits/botstar) - BotStar is a comprehensive chatbot platform for designing, developing, and training chatbots visually on Messenger and websites. It helps businesses automate conversations and customer interactions without coding.
- [Callerapi](https://composio.dev/toolkits/callerapi) - CallerAPI is a white-label caller identification platform for branded caller ID and fraud prevention. It helps businesses boost customer trust while stopping spam, fraud, and robocalls.
- [Callingly](https://composio.dev/toolkits/callingly) - Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources.
- [Callpage](https://composio.dev/toolkits/callpage) - Callpage is a lead capture platform that lets businesses instantly connect with website visitors via callback. It boosts lead generation and increases your sales conversion rates.
- [Clearout](https://composio.dev/toolkits/clearout) - Clearout is an AI-powered service for verifying, finding, and enriching email addresses. It boosts deliverability and helps you discover high-quality leads effortlessly.
- [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.
- [Convolo ai](https://composio.dev/toolkits/convolo_ai) - Convolo ai is an AI-powered communications platform for sales teams. It accelerates lead response and improves conversion rates by automating calls and integrating workflows.
- [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment.
- [Docsbot ai](https://composio.dev/toolkits/docsbot_ai) - Docsbot ai is a platform that lets you build custom AI chatbots trained on your documentation. It automates customer support and content generation, saving time and improving response quality.
- [Findymail](https://composio.dev/toolkits/findymail) - Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment.
- [Freshdesk](https://composio.dev/toolkits/freshdesk) - Freshdesk is customer support software with ticketing and automation tools. It helps teams streamline helpdesk operations for faster, better customer support.
- [Fullenrich](https://composio.dev/toolkits/fullenrich) - FullEnrich is a B2B contact enrichment platform that aggregates emails and phone numbers from 15+ data vendors. Instantly find and verify lead contact data to boost your outreach.
- [Gatherup](https://composio.dev/toolkits/gatherup) - GatherUp is a customer feedback and online review management platform. It helps businesses boost their reputation by streamlining how they collect and manage customer feedback.
- [Getprospect](https://composio.dev/toolkits/getprospect) - Getprospect is a business email discovery tool with LinkedIn integration. Use it to quickly find and verify professional email addresses.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Emelia MCP?

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

### Can I use Tool Router MCP with Mastra AI?

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

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

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

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
