How to integrate Moosend MCP with Claude Agent SDK

This guide walks you through connecting Moosend to the Claude Agent SDK 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 Claude Agent SDK 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 the Claude Agent SDK 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 Claude Agent SDK 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 Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Moosend
  • Configure an AI agent that can use Moosend as a tool
  • Run a live chat session where you can ask the agent to perform Moosend operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Moosend account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • 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 @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Moosend functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

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

  // Create Tool Router session for Moosend
  const session = await composio.create(USER_ID, {
    toolkits: ['moosend'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Moosend
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Moosend tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Moosend
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Moosend and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['moosend']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Moosend tools via Composio.',
    maxTurns: 10,
  };

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Moosend through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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. Claude Agent SDK 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