How to integrate Mailcoach MCP with Vercel AI SDK v6

This guide walks you through connecting Mailcoach to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Mailcoach agent that can create a new email campaign for product launch, add a subscriber to the weekly newsletter list, tag all subscribers interested in webinars through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Mailcoach account through Composio's Mailcoach MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Mailcoach logoMailcoach
Api Key

Mailcoach is an email marketing platform for managing campaigns and subscribers. It helps you reach your audience efficiently with streamlined email delivery and automation.

56 Tools

Introduction

This guide walks you through connecting Mailcoach to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Mailcoach agent that can create a new email campaign for product launch, add a subscriber to the weekly newsletter list, tag all subscribers interested in webinars through natural language commands.

This guide will help you understand how to give your Vercel AI SDK agent real control over a Mailcoach account through Composio's Mailcoach MCP server.

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

Also integrate Mailcoach with

TL;DR

Here's what you'll learn:
  • How to set up and configure a Vercel AI SDK agent with Mailcoach integration
  • Using Composio's Tool Router to dynamically load and access Mailcoach 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 Mailcoach MCP server, and what's possible with it?

The Mailcoach MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mailcoach account. It provides structured and secure access to your email marketing platform, so your agent can manage campaigns, organize subscriber lists, create templates, and automate email workflows on your behalf.

  • Email campaign creation and scheduling: Direct your agent to launch new campaigns, send emails to specific lists, or set up campaign schedules based on your marketing needs.
  • Subscriber list and segmentation management: Let your agent create new email lists, add or confirm subscribers, and apply tags for better audience segmentation and targeting.
  • Template management and customization: Instruct your agent to create, update, or organize reusable email templates and transactional templates for efficient campaign building.
  • Automated suppression and bounce handling: Have your agent add suppressions for bounced or blocked addresses, keeping your lists clean and compliant with deliverability best practices.
  • Bulk subscriber import and data enrichment: Enable your agent to import subscribers via CSV, append new data to existing imports, and streamline growth of your contact lists.

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 you begin, make sure you have:
  • Node.js and npm installed
  • A Composio account with API key
  • An OpenAI API key
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 required dependencies

bash
npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv

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
4

Set up environment variables

bash
OPENAI_API_KEY=your_openai_api_key_here
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here

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
5

Import required modules and validate environment

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,
});
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
6

Create Tool Router session and initialize MCP client

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

  const mcpUrl = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Mailcoach 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 Mailcoach-related tools through the MCP protocol
7

Connect to MCP server and retrieve tools

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();
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 Mailcoach tools that the agent can use
8

Initialize conversation and CLI interface

typescript
let messages: ModelMessage[] = [];

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

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

rl.prompt();
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
9

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

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

Complete Code

Here's the complete code to get you started with Mailcoach and Vercel AI SDK:

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: ["mailcoach"],
  });

  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 mailcoach, 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 Mailcoach 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.
TOOLS

Supported Tools

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

Add Mailcoach Campaign

Tool to create a new Mailcoach campaign.

Add Email List

Tool to create a new email list.

Add suppression

Tool to add a suppression entry.

Add Tag to Email List

Tool to create a new tag within a specific email list.

Add Tags to Subscriber

Add tags to a subscriber for segmentation and targeting.

Add Transactional Email Template

Creates a new email template in Mailcoach via POST /api/templates.

Append to Subscriber Import

Tool to append CSV data to an existing subscriber import.

Confirm Subscriber

Confirm a subscriber's subscription to an email list (double opt-in confirmation).

Create Segment for Email List

Tool to create a new segment within an email list.

Create Subscriber Import

Creates a new subscriber import in Mailcoach.

Delete Campaign

Tool to delete a campaign by UUID.

Delete Email List

Tool to delete an email list by UUID.

Delete Segment from Email List

Tool to delete a segment from an email list.

Delete Subscriber

Permanently delete a subscriber by UUID from Mailcoach.

Delete Subscriber Import

Tool to delete a subscriber import by its UUID.

Delete Suppression

Tool to delete a suppression entry by UUID.

Delete Tag from Email List

Tool to delete a tag from an email list.

Delete Template

Tool to delete a template by UUID.

Delete Transactional Mail

Tool to delete a transactional mail send record by its UUID.

Get All Campaigns

Tool to retrieve all campaigns.

Get All Sent Items

Tool to retrieve all sent items.

Get All Subscriber Imports

Tool to retrieve all subscriber imports.

Get All Suppressions

Retrieve a paginated list of all email suppression entries from Mailcoach.

Get All Tags

Tool to retrieve all tags for a specific email list.

Get All Templates

Tool to retrieve all templates.

Get All Transactional Email Templates

Tool to retrieve all transactional email templates.

Get Campaign Bounces

Tool to retrieve bounced subscribers of a sent campaign with pagination support.

Get Campaign Clicks

Tool to retrieve clicks from a sent campaign with pagination support.

Get Campaign Opens

Tool to retrieve all opens for a sent campaign with pagination support.

Get Campaign Unsubscribes

Tool to retrieve unsubscribes from a sent campaign with pagination support.

Get Email Lists

Tool to retrieve all email lists.

Get Segment

Tool to retrieve details of a specific segment.

Get Specific Campaign

Tool to retrieve details of a specific Mailcoach campaign.

Get Specific Email List

Retrieve detailed information about a specific Mailcoach email list by its UUID.

Get Specific Subscriber

Tool to retrieve a specific subscriber.

Get Specific Suppression

Tool to retrieve a specific suppression entry.

Get Specific Tag

Tool to retrieve details of a specific tag.

Get Specific Template

Retrieves the full details of a specific Mailcoach email template by its UUID.

Get Subscriber Import

Tool to retrieve details of a specific subscriber import by UUID.

Get Transactional Mail

Tool to retrieve details of a specific transactional email by its UUID.

Get User

Tool to retrieve details of the currently authenticated user.

List Segments

Tool to retrieve all segments for a specific email list.

List Subscribers

Tool to list all subscribers from a specific email list with pagination support.

List Transactional Mails

Tool to retrieve all transactional email records.

Remove Tags from Subscriber

Tool to remove tags from a subscriber.

Resend Subscriber Confirmation

Tool to resend confirmation email to a subscriber.

Start Subscriber Import

Starts processing a subscriber import that is in 'draft' status.

Subscribe To Email List

Subscribe (or update) a subscriber to an email list.

Unsubscribe Subscriber

Unsubscribe a subscriber from their email list in Mailcoach.

Update Campaign

Tool to update an existing Mailcoach campaign.

Update Email List

Tool to update an existing email list.

Update Segment

Tool to update an existing segment within an email list.

Update Subscriber

Tool to update a subscriber.

Update Subscriber Import

Tool to update an existing subscriber import.

Update Tag

Tool to update an existing tag within an email list.

Update Template

Updates an existing email template in Mailcoach.

FAQ

Frequently asked questions

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

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 Mailcoach tools.

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

Start with Mailcoach.It takes 30 seconds.

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

Start building