How to integrate Resend MCP with LangChain

This guide walks you through connecting Resend to LangChain using the Composio tool router. By the end, you'll have a working Resend agent that can create a new contact for your newsletter, list all domains connected to your account, cancel a scheduled marketing email through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Resend account through Composio's Resend MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Resend logoResend
Api Key

Resend is a universal API for sending emails using a single, modern endpoint. It streamlines transactional and marketing email delivery for developers and teams.

62 Tools

Introduction

This guide walks you through connecting Resend to LangChain using the Composio tool router. By the end, you'll have a working Resend agent that can create a new contact for your newsletter, list all domains connected to your account, cancel a scheduled marketing email through natural language commands.

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

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

Also integrate Resend with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Resend project to Composio
  • Create a Tool Router MCP session for Resend
  • Initialize an MCP client and retrieve Resend tools
  • Build a LangChain agent that can interact with Resend
  • 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 Resend MCP server, and what's possible with it?

The Resend MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Resend account. It provides structured and secure access to your email sending and contact management capabilities, so your agent can perform actions like sending emails, managing audiences, creating domains, and handling contacts on your behalf.

  • Automated email delivery and scheduling: Ask your agent to send emails instantly or schedule them for later, and even cancel scheduled messages if needed.
  • Audience and contact management: Let your agent create, list, or delete audiences and individual contacts, keeping your recipient lists organized without manual effort.
  • Domain administration: Easily have your agent set up, list, or remove email sending domains, streamlining onboarding or maintenance for your email infrastructure.
  • Seamless recipient segmentation: Direct your agent to group contacts into audiences for targeted campaigns or communications, improving personalization and reach.
  • Bulk operations and cleanups: Enable your agent to quickly list, update, or delete multiple contacts, audiences, or domains to maintain a tidy and up-to-date email system.

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 Resend 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 Resend 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: ['resend']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Resend 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 Resend tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "resend-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 Resend MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Resend 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 Resend 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 Resend 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: ['resend']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "resend-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 Resend 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 Resend 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 Resend action and event your agent gets out of the box.

Add Contact To Segment

Add an existing contact to a segment in Resend.

Cancel Email

Cancel a scheduled email.

Create API Key

Create a new API key to authenticate communications with Resend.

Create Audience

Create a list of contacts.

Create Contact

Create a contact in Resend.

Create Contact Property

Tool to create a new contact property in Resend.

Create Contact V2

Tool to create a new contact in Resend.

Create Domain

Create a domain through the Resend Email API.

Create Template

Tool to create a new email template in Resend.

Create Topic

Tool to create a new topic to segment your audience.

Create Webhook

Tool to create a webhook to receive real-time notifications about email events.

Delete API Key

Remove an existing API key from Resend.

Delete Audience

Remove an existing audience.

Delete Contact

Delete a contact in Resend.

Delete Contact By ID

Tool to remove an existing contact by its ID.

Delete Contact Property

Remove an existing contact property from Resend.

Delete Domain

Delete a domain through the Resend Email API.

Delete Segment

Remove an existing segment.

Delete Template

Remove an existing template.

Delete Topic

Tool to remove an existing topic in Resend.

Delete Webhook

Remove an existing webhook.

Duplicate Template

Duplicate an existing template through the Resend Email API.

Get Contact

Tool to retrieve a single contact from Resend by ID or email.

Get Contact Property

Tool to retrieve a single contact property from Resend.

Get Email Attachment

Retrieve a single attachment from a sent email.

Get Segment

Retrieve a single segment by its ID.

Get Template

Retrieve a single template by ID or alias from Resend.

Get Topic

Tool to retrieve a single topic by its ID in Resend.

Get Webhook

Retrieve a single webhook for the authenticated user.

List All Contacts

Tool to retrieve a list of all contacts from Resend.

List API Keys

Tool to retrieve a list of API keys for the authenticated user.

List Audiences

List all audiences.

List Broadcasts

Tool to retrieve a list of broadcasts.

List Contact Properties

Tool to retrieve a list of contact properties from Resend.

List Contacts

List contacts in Resend.

List Contact Segments

Retrieve a list of segments that a contact is part of.

List Contact Topics

Retrieve a list of topic subscriptions for a contact in Resend.

List Domains

List all domains.

List Email Attachments

Tool to retrieve a list of attachments from a sent email.

List Emails

Tool to retrieve a list of emails sent by your team.

List Received Emails

Tool to retrieve a list of received emails for the authenticated user.

List Segments

Tool to retrieve a list of segments from Resend.

List Templates

Tool to retrieve a list of templates from Resend.

List Topics

Tool to retrieve a list of topics for the authenticated user.

List Webhooks

Retrieve a list of webhooks for the authenticated user.

Publish Template

Publish a template through the Resend Email API.

Remove Contact From Segment

Remove an existing contact from a segment.

Retrieve Audience

Retrieve a single audience.

Retrieve Contact

Retrieve a contact in Resend.

Retrieve Domain

Retrieve a single domain.

Retrieve Email

Retrieve a single email.

Send Batch Emails

Trigger up to 100 batch emails at once.

Send Email

Send an email using Resend.

Update Broadcast

Update an existing broadcast in Resend.

Update Contact

Tool to update an existing contact in Resend by ID or email.

Update Contact Property

Update an existing contact property in Resend.

Update Domain

Update an existing domain.

Update Email

Update a scheduled email.

Update Template

Tool to update an existing email template in Resend.

Update Topic

Tool to update an existing topic in Resend.

Update Webhook

Tool to update an existing webhook configuration.

Verify Domain

Verify a domain through the Resend Email API.

FAQ

Frequently asked questions

With a standalone Resend MCP server, the agents and LLMs can only access a fixed set of Resend tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Resend 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 Resend tools.

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

Start with Resend.It takes 30 seconds.

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

Start building