# How to integrate Moosend MCP with Vercel AI SDK v6

```json
{
  "title": "How to integrate Moosend MCP with Vercel AI SDK v6",
  "toolkit": "Moosend",
  "toolkit_slug": "moosend",
  "framework": "Vercel AI SDK",
  "framework_slug": "ai-sdk",
  "url": "https://composio.dev/toolkits/moosend/framework/ai-sdk",
  "markdown_url": "https://composio.dev/toolkits/moosend/framework/ai-sdk.md",
  "updated_at": "2026-05-12T10:19:27.420Z"
}
```

## Introduction

This guide walks you through connecting Moosend to Vercel AI SDK v6 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 Vercel AI 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

- [OpenAI Agents SDK](https://composio.dev/toolkits/moosend/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/moosend/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/moosend/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/moosend/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/moosend/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/moosend/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/moosend/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/moosend/framework/cli)
- [Google ADK](https://composio.dev/toolkits/moosend/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/moosend/framework/langchain)
- [Mastra AI](https://composio.dev/toolkits/moosend/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/moosend/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/moosend/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- How to set up and configure a Vercel AI SDK agent with Moosend integration
- Using Composio's Tool Router to dynamically load and access Moosend tools
- Creating an MCP client connection using HTTP transport
- Building an interactive CLI chat interface with conversation history management
- Handling tool calls and results within the Vercel AI SDK framework

## What is Vercel AI SDK?

The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state.
Key features include:
- streamText: Core function for streaming responses with real-time tool support
- MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp
- Step Counting: Control multi-step tool execution with stopWhen: stepCountIs()
- OpenAI Provider: Native integration with OpenAI models

## 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.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `MOOSEND_ADD_SEGMENT_CRITERIA` | Add Segment Criteria | Tool to add a new criterion (rule) to a segment. Use after obtaining the mailing list ID and segment ID to define filtering criteria. |
| `MOOSEND_ADD_SUBSCRIBER` | Add or Update Subscriber | Tool to add or update a subscriber in a mailing list. Use after obtaining the mailing list ID to manage subscribers. |
| `MOOSEND_CLONE_CAMPAIGN` | Clone Campaign | Tool to clone an existing campaign, creating an exact copy with the same content and settings. Use when you want to reuse a campaign template or create variations of an existing campaign. The cloned campaign is created as a new draft that can be modified independently. |
| `MOOSEND_CREATE_CUSTOM_FIELD` | Create custom field | Tool to create a custom field in a mailing list. Use when you need to define a new custom field for subscriber data. |
| `MOOSEND_CREATE_MAILING_LIST` | Create Mailing List | Tool to create a new empty mailing list in Moosend. Use after obtaining API key. |
| `MOOSEND_CREATE_SEGMENT` | Create Segment | Tool to create a new segment for a mailing list. Use to organize subscribers based on criteria or create empty segments for future use. |
| `MOOSEND_DELETE_CAMPAIGN` | Delete Campaign | Permanently deletes a campaign from your Moosend account by its ID. This action removes draft or sent campaigns irreversibly. Use this when you need to clean up campaigns that are no longer needed. The campaign ID can be obtained from listing campaigns or retrieved when a campaign is created. Always verify the campaign ID before deletion as this operation cannot be undone. |
| `MOOSEND_DELETE_CUSTOM_FIELD` | Delete custom field | Tool to remove a custom field definition from a mailing list. Use when you have confirmed the custom field ID to delete. |
| `MOOSEND_DELETE_MAILING_LIST` | Delete Mailing List | Tool to delete a mailing list. Use when you need to permanently remove a mailing list from your Moosend account after confirming its ID. Deletion is irreversible. |
| `MOOSEND_GET_ALL_CAMPAIGNS` | Get all campaigns | Tool to retrieve a list of all campaigns in your account. Use after acquiring valid API credentials to explore campaign data. |
| `MOOSEND_GET_ALL_SUBSCRIBERS` | Get All Subscribers | Retrieves all subscribers from a specified mailing list, filtered by their subscription status (Subscribed, Unsubscribed, Bounced, or Removed). Returns paginated results with subscriber details including email, name, custom fields, and subscription timestamps. |
| `MOOSEND_GET_CAMPAIGN_DETAILS` | Get Campaign Details | Retrieves comprehensive details about a specific campaign by its ID. Returns complete campaign information including configuration, status, content, and settings. Use this when you need to inspect or verify campaign properties. |
| `MOOSEND_GET_CAMPAIGN_STATS_BY_LOCATION` | Get Campaign Stats by Location | Retrieves a detailed report of campaign opens (unique and total) by country. Use this when you need to analyze the geographic distribution of email campaign engagement. |
| `MOOSEND_GET_MAILING_LIST_DETAILS` | Get Mailing List Details | Gets details for a given mailing list including name, member counts, status, and custom field definitions. Optionally include subscriber statistics. Use this when you need to inspect mailing list properties or verify list configuration. |
| `MOOSEND_GET_SUBSCRIBER_BY_EMAIL` | Get Subscriber By Email | Retrieves detailed subscriber information by email address from a specific mailing list. Returns comprehensive subscriber data including ID, name, subscription status, custom fields, tags, preferences, and timestamps for creation, updates, and unsubscribe events. Use this when you need to: - Look up a subscriber's details using their email address - Check if an email is already subscribed to a list - Retrieve custom field values for a subscriber - Check subscription status and history Example: "Get subscriber details for jane.doe@example.com in list 04fad8e2-..." |
| `MOOSEND_LIST_ALL_MAILING_LISTS` | List all mailing lists | Tool to get a list of your active mailing lists in your account. Use after acquiring valid API credentials to explore mailing list data. Optionally include statistics and sort results by various fields. |
| `MOOSEND_LIST_ALL_SENDERS` | List all senders | Tool to retrieve a list of all active senders in your account. Use when you need to view available sender email addresses for campaigns. |
| `MOOSEND_LIST_CAMPAIGNS_WITH_PAGING` | List campaigns with paging | Tool to retrieve a paginated list of all campaigns in your account with detailed information. Use when you need to fetch campaigns with specific page size and sorting options. Paging information is required as input. |
| `MOOSEND_LIST_SEGMENTS` | List Segments | Tool to get a list of all segments with their criteria for a specified mailing list. Use when you need to retrieve segment definitions for targeting specific subscriber groups. |
| `MOOSEND_REMOVE_MULTIPLE_SUBSCRIBERS` | Remove Multiple Subscribers | Tool to permanently remove multiple subscribers from a mailing list. Use when you need to delete multiple subscribers permanently without adding them to the suppression list. Invalid email addresses are automatically ignored. |
| `MOOSEND_SCHEDULE_CAMPAIGN` | Schedule Campaign | Tool to schedule a campaign. Use when you want to set a specific date and time for campaign delivery after confirming its ID. |
| `MOOSEND_SEND_CAMPAIGN` | Send Campaign | Tool to send an existing draft campaign immediately. Use when you want to dispatch a campaign to all recipients after final review. |
| `MOOSEND_UNSCHEDULE_CAMPAIGN` | Unschedule Campaign | Tool to unschedule a campaign. Removes a previously defined scheduled date and time from a campaign, so that it will be delivered immediately if already queued or when sent. |
| `MOOSEND_UNSUBSCRIBE_FROM_ACCOUNT` | Unsubscribe From Account | Tool to unsubscribe a subscriber from the account. Use when you need to remove a subscriber from all mailing lists. Note: Rate limit is 20 requests per 10 seconds per API key. |
| `MOOSEND_UNSUBSCRIBE_FROM_MAILING_LIST` | Unsubscribe from Mailing List | Tool to unsubscribe a subscriber from a specified mailing list. Use when you need to remove a subscriber's active subscription. Rate limit: 20 requests per 10 seconds per API key. |
| `MOOSEND_UPDATE_CAMPAIGN` | Update Campaign | Tool to update a draft campaign. Use when you want to modify properties of an existing draft campaign before sending. |
| `MOOSEND_UPDATE_CUSTOM_FIELD` | Update custom field | Tool to update properties of an existing custom field in a mailing list. Use after confirming mailing list and custom field IDs. |
| `MOOSEND_UPDATE_MAILING_LIST` | Update Mailing List | Tool to update the properties of an existing mailing list. Use when you need to change list metadata after confirming the list ID. |
| `MOOSEND_UPDATE_SEGMENT` | Update Segment | Tool to update properties and criteria of an existing segment. Use when you need to modify segment name, match type, or filtering criteria. |
| `MOOSEND_UPDATE_SEGMENT_CRITERIA` | Update Segment Criteria | Tool to update an existing criterion in a segment. Use when you need to modify filtering rules for a mailing list segment. |
| `MOOSEND_UPDATE_SUBSCRIBER` | Update Subscriber | Tool to update a subscriber in the specified mailing list. Use when you need to modify subscriber information like email, name, or custom fields. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Moosend MCP server is an implementation of the Model Context Protocol that connects your AI agent to Moosend. It provides structured and secure access so your agent can perform Moosend operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before you begin, make sure you have:
- Node.js and npm installed
- A Composio account with API key
- An OpenAI API key

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install required dependencies

First, install the necessary packages for your project.
What you're installing:
- @ai-sdk/openai: Vercel AI SDK's OpenAI provider
- @ai-sdk/mcp: MCP client for Vercel AI SDK
- @composio/core: Composio SDK for tool integration
- ai: Core Vercel AI SDK
- dotenv: Environment variable management
```bash
npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's needed:
- OPENAI_API_KEY: Your OpenAI API key for GPT model access
- COMPOSIO_API_KEY: Your Composio API key for tool access
- COMPOSIO_USER_ID: A unique identifier for the user session
```bash
OPENAI_API_KEY=your_openai_api_key_here
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
```

### 4. Import required modules and validate environment

What's happening:
- We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio
- The dotenv/config import automatically loads environment variables
- The MCP client import enables connection to Composio's tool server
```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});
```

### 5. Create Tool Router session and initialize MCP client

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 mcp object contains the URL and authentication headers needed to connect to the MCP server
- This session provides access to all Moosend-related tools through the MCP protocol
```typescript
async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["moosend"],
  });

  const mcpUrl = session.mcp.url;
```

### 6. Connect to MCP server and retrieve tools

What's happening:
- We're creating an MCP client that connects to our Composio Tool Router session via HTTP
- The mcp.url provides the endpoint, and mcp.headers contains authentication credentials
- The type: "http" is important - Composio requires HTTP transport
- tools() retrieves all available Moosend tools that the agent can use
```typescript
const mcpClient = await createMCPClient({
  transport: {
    type: "http",
    url: mcpUrl,
    headers: session.mcp.headers, // Authentication headers for the Composio MCP server
  },
});

const tools = await mcpClient.tools();
```

### 7. Initialize conversation and CLI interface

What's happening:
- We initialize an empty messages array to maintain conversation history
- A readline interface is created to accept user input from the command line
- Instructions are displayed to guide the user on how to interact with the agent
```typescript
let messages: ModelMessage[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log(
  "Ask any questions related to moosend, like summarize my last 5 emails, send an email, etc... :)))\n",
);

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

rl.prompt();
```

### 8. Handle user input and stream responses with real-time tool feedback

What's happening:
- We use streamText instead of generateText to stream responses in real-time
- toolChoice: "auto" allows the model to decide when to use Moosend tools
- stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations
- onStepFinish callback displays which tools are being used in real-time
- We iterate through the text stream to create a typewriter effect as the agent responds
- The complete response is added to conversation history to maintain context
- Errors are caught and displayed with helpful retry suggestions
```typescript
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;
  }

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

  try {
    const stream = streamText({
      model: openai("gpt-5"),
      messages,
      tools,
      toolChoice: "auto",
      stopWhen: stepCountIs(10),
      onStepFinish: (step) => {
        for (const toolCall of step.toolCalls) {
          console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

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

## Complete Code

```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

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

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["moosend"],
  });

  const mcpUrl = session.mcp.url;

  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      url: mcpUrl,
      headers: session.mcp.headers, // Authentication headers for the Composio MCP server
    },
  });

  const tools = await mcpClient.tools();

  let messages: ModelMessage[] = [];

  console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
  console.log(
    "Ask any questions related to moosend, like summarize my last 5 emails, send an email, etc... :)))\n",
  );

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

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

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

    try {
      const stream = streamText({
        model: openai("gpt-5"),
        messages,
        tools,
        toolChoice: "auto",
        stopWhen: stepCountIs(10),
        onStepFinish: (step) => {
          for (const toolCall of step.toolCalls) {
            console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

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

## Conclusion

You've successfully built a Moosend agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback.
Key features of this implementation:
- Real-time streaming responses for a better user experience with typewriter effect
- Live tool execution feedback showing which tools are being used as the agent works
- Dynamic tool loading through Composio's Tool Router with secure authentication
- Multi-step tool execution with configurable step limits (up to 10 steps)
- Comprehensive error handling for robust agent execution
- Conversation history maintenance for context-aware responses
You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

## How to build Moosend MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/moosend/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/moosend/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/moosend/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/moosend/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/moosend/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/moosend/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/moosend/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/moosend/framework/cli)
- [Google ADK](https://composio.dev/toolkits/moosend/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/moosend/framework/langchain)
- [Mastra AI](https://composio.dev/toolkits/moosend/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/moosend/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/moosend/framework/crew-ai)

## Related Toolkits

- [Reddit](https://composio.dev/toolkits/reddit) - Reddit is a social news platform with thriving user-driven communities (subreddits). It's the go-to place for discussion, content sharing, and viral marketing.
- [Facebook](https://composio.dev/toolkits/facebook) - Facebook is a social media and advertising platform for businesses and creators. It helps you connect, share, and manage content across your public Facebook Pages.
- [Linkedin](https://composio.dev/toolkits/linkedin) - LinkedIn is a professional networking platform for connecting, sharing content, and engaging with business opportunities. It's the go-to place for building your professional brand and unlocking new career connections.
- [Active campaign](https://composio.dev/toolkits/active_campaign) - ActiveCampaign is a marketing automation and CRM platform for managing email campaigns, sales pipelines, and customer segmentation. It helps businesses engage customers and drive growth through smart automation and targeted outreach.
- [ActiveTrail](https://composio.dev/toolkits/active_trail) - ActiveTrail is a user-friendly email marketing and automation platform. It helps you reach subscribers and automate campaigns with ease.
- [Ahrefs](https://composio.dev/toolkits/ahrefs) - Ahrefs is an SEO and marketing platform for site audits, keyword research, and competitor insights. It helps you improve search rankings and drive organic traffic.
- [Amcards](https://composio.dev/toolkits/amcards) - AMCards lets you create and mail personalized greeting cards online. Build stronger customer relationships with easy, automated card campaigns.
- [Beamer](https://composio.dev/toolkits/beamer) - Beamer is a news and changelog platform for in-app announcements and feature updates. It helps companies boost user engagement by sharing news where users are most active.
- [Benchmark email](https://composio.dev/toolkits/benchmark_email) - Benchmark Email is a platform for creating, sending, and tracking email campaigns. It's built to help you engage audiences and analyze results—all in one place.
- [Bigmailer](https://composio.dev/toolkits/bigmailer) - BigMailer is an email marketing platform for managing multiple brands with white-labeling and automation. It helps teams streamline campaigns and simplify integration with Amazon SES.
- [Brandfetch](https://composio.dev/toolkits/brandfetch) - Brandfetch is an API that delivers company logos, colors, and visual branding assets. It helps marketers and developers keep brand visuals consistent everywhere.
- [Brevo](https://composio.dev/toolkits/brevo) - Brevo is an all-in-one email and SMS marketing platform for transactional messaging, automation, and CRM. It helps businesses engage customers and streamline communications through powerful campaign tools.
- [Campayn](https://composio.dev/toolkits/campayn) - Campayn is an email marketing platform for creating, sending, and managing campaigns. It helps businesses engage contacts and grow audiences with easy-to-use tools.
- [Cardly](https://composio.dev/toolkits/cardly) - Cardly is a platform for creating and sending personalized direct mail to customers. It helps businesses break through the digital clutter by getting real engagement via physical mailboxes.
- [ClickSend](https://composio.dev/toolkits/clicksend) - ClickSend is a cloud-based SMS and email marketing platform for businesses. It streamlines communication by enabling quick message delivery and contact management.
- [Crustdata](https://composio.dev/toolkits/crustdata) - CrustData is an AI-powered data intelligence platform for real-time company and people data. It helps B2B sales teams, AI SDRs, and investors react to live business signals.
- [Curated](https://composio.dev/toolkits/curated) - Curated is a platform for collecting, curating, and publishing newsletters. It streamlines content aggregation and distribution for creators and teams.
- [Customerio](https://composio.dev/toolkits/customerio) - Customer.io is a customer engagement platform for targeted messaging across email, SMS, and push. Easily automate, segment, and track communications with your audience.
- [Cutt ly](https://composio.dev/toolkits/cutt_ly) - Cutt.ly is a URL shortening service for managing and analyzing links. Streamline your workflows with quick, trackable, and branded short URLs.
- [Demio](https://composio.dev/toolkits/demio) - Demio is webinar software built for marketers, offering both live and automated sessions with interactive features. It helps teams engage audiences and optimize lead generation through detailed analytics.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Moosend MCP?

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.

### Can I use Tool Router MCP with Vercel AI SDK v6?

Yes, you can. Vercel AI SDK v6 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.

### Can I manage the permissions and scopes for Moosend while using Tool Router?

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.

### How safe is my data with Composio Tool Router?

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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
