How to integrate Moosend MCP with LangChain

This guide walks you through connecting Moosend to LangChain using the Composio tool router. By the end, you'll have a working Moosend agent that can add new subscriber to welcome list, get all campaigns sent last month, retrieve details for summer sale campaign through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Moosend account through Composio's Moosend MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Moosend logoMoosend
Api Key

Moosend is a cloud-based, AI-powered email marketing platform for automated campaigns. Reach your audience efficiently with personalization, analytics, and powerful segmentation.

31 Tools

Introduction

This guide walks you through connecting Moosend to LangChain using the Composio tool router. By the end, you'll have a working Moosend agent that can add new subscriber to welcome list, get all campaigns sent last month, retrieve details for summer sale campaign through natural language commands.

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

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

Also integrate Moosend with

TL;DR

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

The Moosend MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Moosend account. It provides structured and secure access to your email marketing platform, so your agent can perform actions like managing subscribers, automating campaigns, creating mailing lists, and customizing audience data on your behalf.

  • Subscriber management and segmentation: Add, update, or search for subscribers in your mailing lists, letting your agent keep your audience organized and up to date.
  • Campaign creation and analytics: Retrieve, inspect, and manage email campaigns—enabling your agent to help you monitor, review, or even clean up your marketing activities.
  • Mailing list automation: Create or delete mailing lists as needed, so your agent can reorganize or streamline your audience targeting at scale.
  • Custom fields and personalization: Build or remove custom fields in your lists, empowering the agent to personalize campaigns and collect richer subscriber data.
  • Campaign and list cleanup: Direct your agent to permanently remove campaigns or mailing lists you no longer need, keeping your marketing hub tidy and efficient.

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 Moosend 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 Moosend 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: ['moosend']
    }
);

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

Configure the agent with the MCP URL

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

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

Add Segment Criteria

Tool to add a new criterion (rule) to a segment.

Add or Update Subscriber

Tool to add or update a subscriber in a mailing list.

Clone Campaign

Tool to clone an existing campaign, creating an exact copy with the same content and settings.

Create custom field

Tool to create a custom field in a mailing list.

Create Mailing List

Tool to create a new empty mailing list in Moosend.

Create Segment

Tool to create a new segment for a mailing list.

Delete Campaign

Permanently deletes a campaign from your Moosend account by its ID.

Delete custom field

Tool to remove a custom field definition from a mailing list.

Delete Mailing List

Tool to delete a mailing list.

Get all campaigns

Tool to retrieve a list of all campaigns in your account.

Get All Subscribers

Retrieves all subscribers from a specified mailing list, filtered by their subscription status (Subscribed, Unsubscribed, Bounced, or Removed).

Get Campaign Details

Retrieves comprehensive details about a specific campaign by its ID.

Get Campaign Stats by Location

Retrieves a detailed report of campaign opens (unique and total) by country.

Get Mailing List Details

Gets details for a given mailing list including name, member counts, status, and custom field definitions.

Get Subscriber By Email

Retrieves detailed subscriber information by email address from a specific mailing list.

List all mailing lists

Tool to get a list of your active mailing lists in your account.

List all senders

Tool to retrieve a list of all active senders in your account.

List campaigns with paging

Tool to retrieve a paginated list of all campaigns in your account with detailed information.

List Segments

Tool to get a list of all segments with their criteria for a specified mailing list.

Remove Multiple Subscribers

Tool to permanently remove multiple subscribers from a mailing list.

Schedule Campaign

Tool to schedule a campaign.

Send Campaign

Tool to send an existing draft campaign immediately.

Unschedule Campaign

Tool to unschedule a campaign.

Unsubscribe From Account

Tool to unsubscribe a subscriber from the account.

Unsubscribe from Mailing List

Tool to unsubscribe a subscriber from a specified mailing list.

Update Campaign

Tool to update a draft campaign.

Update custom field

Tool to update properties of an existing custom field in a mailing list.

Update Mailing List

Tool to update the properties of an existing mailing list.

Update Segment

Tool to update properties and criteria of an existing segment.

Update Segment Criteria

Tool to update an existing criterion in a segment.

Update Subscriber

Tool to update a subscriber in the specified mailing list.

FAQ

Frequently asked questions

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

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

Start with Moosend.It takes 30 seconds.

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

Start building