How to integrate Mailtrap MCP with LlamaIndex

This guide walks you through connecting Mailtrap to LlamaIndex using the Composio tool router. By the end, you'll have a working Mailtrap agent that can send a test email to marketing team, list all emails sent from mailtrap today, create a new inbox for transactional testing through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Mailtrap account through Composio's Mailtrap MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Mailtrap logoMailtrap
Api KeyApi Key

Mailtrap is an email delivery platform for safe email testing and transactional email sending. It helps you catch bugs and verify email flows without spamming real inboxes.

49 Tools

Introduction

This guide walks you through connecting Mailtrap to LlamaIndex using the Composio tool router. By the end, you'll have a working Mailtrap agent that can send a test email to marketing team, list all emails sent from mailtrap today, create a new inbox for transactional testing through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Mailtrap account through Composio's Mailtrap MCP server.

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

Also integrate Mailtrap with

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Mailtrap
  • Connect LlamaIndex to the Mailtrap MCP server
  • Build a Mailtrap-powered agent using LlamaIndex
  • Interact with Mailtrap through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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

The Mailtrap MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mailtrap account. It provides structured and secure access so your agent can perform Mailtrap operations on your behalf.

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 step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Mailtrap account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Mailtrap

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Mailtrap access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called mailtrap_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

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

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["mailtrap"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Mailtrap actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, mailtrap)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Mailtrap tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Mailtrap
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Mailtrap tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Mailtrap
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Mailtrap, then start asking questions.

Complete Code

Here's the complete code to get you started with Mailtrap and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["mailtrap"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Mailtrap actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Mailtrap to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Mailtrap tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

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

Clean Inbox

Tool to clean an inbox in Mailtrap by deleting all messages.

Create Contact

Tool to create a new contact in Mailtrap.

Create Contact Event

Tool to create a contact event in Mailtrap.

Create Contact Export

Tool to create a contact export job for a Mailtrap account.

Create Contact Field

Tool to create a custom contact field in Mailtrap.

Create Contact List

Tool to create a new contact list in Mailtrap.

Create Email Template

Tool to create a new email template in Mailtrap account.

Create Sending Domain

Tool to create a new sending domain in Mailtrap.

Delete Contact

Tool to delete a contact from a Mailtrap account.

Delete Contact Field

Tool to delete a contact field by its ID.

Delete Contact List

Tool to delete a contact list by its ID.

Delete Email Template

Tool to delete an email template from a Mailtrap account.

Delete Project

Tool to delete a project from Mailtrap.

Delete Sending Domain

Tool to delete a sending domain from a Mailtrap account.

Get Billing Usage

Tool to retrieve current billing cycle usage for an account.

Get Contact

Tool to retrieve a contact by UUID or email address from Mailtrap.

Get Contact Export

Tool to retrieve the status of a contact export.

Get Contact Field

Tool to retrieve contact field details by field ID.

Get Contact Import Status

Tool to retrieve the status of a contact import operation.

Get Contact List

Tool to retrieve a specific contact list by its ID.

Get Email Template

Tool to retrieve details of a specific email template by ID.

Get Inbox Attributes

Tool to retrieve inbox attributes from Mailtrap.

Get Message HTML Body

Tool to retrieve the HTML body of a message from Mailtrap.

Get Permission Resources

Tool to retrieve all resources in account for permission management.

Get Project by ID

Tool to retrieve project details from Mailtrap by project ID.

Get Sending Domain

Tool to retrieve sending domain details from Mailtrap.

Get Sending Stats

Tool to retrieve email sending statistics from Mailtrap for a specific account.

Get Sending Stats by Categories

Tool to retrieve email sending statistics grouped by categories.

Get Sending Stats by Date

Tool to retrieve email sending statistics aggregated by date.

Get Sending Stats by Domains

Tool to retrieve sending statistics grouped by domains for a Mailtrap account.

Get Sending Stats by ESP

Tool to retrieve email sending statistics grouped by email service providers (ESPs) for a specified date range.

Import Contacts

Tool to import contacts in bulk to Mailtrap.

List Accounts

Tool to list all Mailtrap accounts you have access to.

List Contact Fields

Tool to get all contact fields for a Mailtrap account.

List Contact Lists

Tool to retrieve all contact lists for a Mailtrap account.

List Email Templates

Tool to retrieve all email templates for a Mailtrap account.

List Inboxes

Tool to get a list of inboxes for a Mailtrap account.

List Messages in Inbox

Tool to get messages from a Mailtrap inbox.

List Projects

Tool to get a list of projects for a Mailtrap account.

List Sending Domains

Tool to list all sending domains for a Mailtrap account.

List Email Suppressions

Tool to list suppressed email addresses for a Mailtrap account.

Mark Inbox as Read

Tool to mark all messages in a Mailtrap inbox as read.

Reset Inbox Credentials

Tool to reset SMTP credentials for a Mailtrap inbox.

Update contact

Tool to update an existing contact in Mailtrap.

Update Contact Field

Tool to update a contact field in Mailtrap.

Update Contact List

Tool to update a contact list's name in Mailtrap.

Update Email Template

Tool to update an existing email template in Mailtrap account.

Update inbox

Tool to update an inbox's settings in Mailtrap.

Update project

Tool to update a project's name in Mailtrap.

FAQ

Frequently asked questions

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

Yes, you can. LlamaIndex 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 Mailtrap tools.

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

Start with Mailtrap.It takes 30 seconds.

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

Start building