SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Mailersend MCP with LangChain

Connect LangChain to Mailersend MCP. Add a new sending domain for your app, list all smtp users for our domain, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Mailersend logoMailersend
Api Key

MailerSend is a transactional email platform for developers to send, receive, and track emails via API. It provides reliable deliverability, analytics, and easy integration for your apps.

23 Tools

Introduction

This guide walks you through connecting Mailersend to LangChain using the Composio tool router. By the end, you'll have a working Mailersend agent that can create sending domains and SMTP users, list sent messages, check SMS activity, browse email templates, and manage webhooks through natural language commands.

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

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

Also integrate Mailersend with

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKGrok BotCodexOpenClawHermesAtomic AgentGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Mailersend project to Composio
  • Create a Tool Router MCP session for Mailersend
  • Initialize an MCP client and retrieve Mailersend tools
  • Build a LangChain agent that can interact with Mailersend
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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

The Mailersend MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mailersend account. It provides structured and secure access to your transactional email infrastructure, so your agent can perform actions like sending emails, managing domains, configuring webhooks, and monitoring API usage on your behalf.

  • Seamless domain management: Register new sending domains, verify their status, and retrieve detailed configuration information to ensure reliable email delivery.
  • Automated email and SMTP user setup: Quickly create SMTP users and API tokens as needed for secure and scalable application integration.
  • Webhook configuration and event tracking: Set up and delete webhooks to monitor real-time email events such as sent, delivered, or opened messages, enabling proactive workflows and notifications.
  • Recipient and quota insights: List recipients for specific domains and monitor your API usage to stay within account limits and optimize deliverability.
  • Centralized resource discovery: Retrieve general API resources and overview endpoints to streamline Mailersend integration and administration directly from your agent.

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 starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_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's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Mailersend functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Mailersend tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['mailersend']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Mailersend tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Mailersend tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "mailersend-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Mailersend MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Mailersend tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Mailersend related question or task to the agent.\n");

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

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;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Mailersend and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['mailersend']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "mailersend-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Mailersend related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    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;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

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

Conclusion

You've successfully built a LangChain agent that can interact with Mailersend through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

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

Create Sending Domain

Tool to add a new sending domain to MailerSend.

Create SMTP User

Tool to create a new SMTP user.

Create API Token

Creates a new API token with specified scopes (permissions) for a domain.

Create Webhook

Tool to create a new webhook for a MailerSend domain.

Delete Webhook

Tool to delete an existing webhook.

Get API Quota

Tool to retrieve current API usage quota.

Get Domain

Tool to retrieve detailed information about a specific sending domain in MailerSend.

List Domain Recipients

Tool to list recipients for a domain.

Get sending domains

Retrieve a paginated list of all sending domains configured in your MailerSend account.

Get general API resources

Retrieve general API resource categories and endpoint information.

List Sender Identities

Retrieves a paginated list of sender identities configured in your MailerSend account.

Get sent messages

Tool to retrieve a paginated list of sent messages.

Get email recipients

Tool to retrieve a list of email recipients.

Get SMS Activity

Tool to retrieve SMS activity logs.

Get SMS Inbounds

Retrieve inbound SMS route configurations.

List SMS Messages

Retrieves a paginated list of SMS messages sent through the MailerSend API.

Get SMS Numbers

Tool to retrieve a paginated list of SMS phone numbers.

Get SMS recipients

Tool to retrieve a list of SMS recipients.

Get SMTP users

Retrieve a paginated list of SMTP users for a specified domain.

Get email templates

Retrieves a paginated list of email templates from your MailerSend account.

Get API Tokens

Retrieves a paginated list of API tokens associated with your MailerSend account.

Get users

Tool to retrieve a list of users associated with your account.

List webhooks

Tool to retrieve a list of webhooks.

FRAMEWORKS

How to build Mailersend MCP Agent with another framework

Claude Code logo

Claude Code

Use Mailersend MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Mailersend MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Mailersend MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Mailersend MCP with Claude Agent SDK

Grok Bot logo

Grok Bot

Use Mailersend MCP with Grok Bot

Codex logo

Codex

Use Mailersend MCP with Codex

OpenClaw logo

OpenClaw

Use Mailersend MCP with OpenClaw

Hermes logo

Hermes

Use Mailersend MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Mailersend MCP with Atomic Agent

Google ADK logo

Google ADK

Use Mailersend MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Mailersend MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Mailersend MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Mailersend MCP with LlamaIndex

CrewAI logo

CrewAI

Use Mailersend MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Mailersend MCP with Pydantic AI

AutoGen logo

AutoGen

Use Mailersend MCP with AutoGen

FAQ

Frequently asked questions

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

Yes, you can. LangChain 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 Mailersend tools.

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

Start with Mailersend.It takes 30 seconds.

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

Start building