How to integrate Bigmailer MCP with Claude Agent SDK

This guide walks you through connecting Bigmailer to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Bigmailer agent that can create a new welcome campaign for brand x, list all brands i manage in bigmailer, get your bigmailer account user details through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Bigmailer account through Composio's Bigmailer MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Bigmailer logoBigmailer
Api Key

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.

57 Tools

Introduction

This guide walks you through connecting Bigmailer to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Bigmailer agent that can create a new welcome campaign for brand x, list all brands i manage in bigmailer, get your bigmailer account user details through natural language commands.

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

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

Also integrate Bigmailer 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 Bigmailer
  • Configure an AI agent that can use Bigmailer as a tool
  • Run a live chat session where you can ask the agent to perform Bigmailer 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 Bigmailer MCP server, and what's possible with it?

The Bigmailer MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Bigmailer account. It provides structured and secure access to your email marketing platform, so your agent can perform actions like creating transactional campaigns, retrieving your brands, and managing user account details on your behalf.

  • Automated transactional campaign creation: Have your agent quickly set up new transactional email campaigns for any of your brands, with full control over content, sender details, and subject lines.
  • Brand management and discovery: Let your agent list and organize all brands associated with your Bigmailer account, providing a clear overview for multi-brand operations.
  • User account information retrieval: Easily check your authenticated user details to verify API connectivity and view essential account information in real time.
  • Multi-brand marketing workflow automation: Empower your agent to streamline campaign launches and brand management across multiple business entities from one place.

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 Bigmailer 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 Bigmailer 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 Bigmailer
  const session = await composio.create(USER_ID, {
    toolkits: ['bigmailer'],
  });
  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 Bigmailer
  • 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 Bigmailer 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 Bigmailer
  • 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 Bigmailer 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: ['bigmailer']
  });
  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 Bigmailer 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 Bigmailer 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 Bigmailer action and event your agent gets out of the box.

Create Brand

Tool to create a new brand in BigMailer.

Create Brand Property

Tool to create a brand property in BigMailer.

Create Bulk Campaign

Tool to create a bulk email campaign in BigMailer.

Create Contact

Tool to create a new contact in BigMailer within a specified brand.

Create Contact Batch

Tool to create a batch of contacts in BigMailer for a specific brand.

Create Field

Tool to create a custom field in a BigMailer brand.

Create List

Creates a new contact list within a specified brand in BigMailer.

Create Segment

Tool to create a segment in BigMailer for a specific brand.

Create Suppression List

Tool to upload a suppression list for a brand in BigMailer.

Create Template

Tool to create a new email or page template in BigMailer.

Create Transactional Campaign

Creates a new transactional campaign within a specified brand in BigMailer.

Create User

Tool to create a new user in BigMailer.

Delete Brand Property

Tool to delete a brand property from a brand in BigMailer.

Delete Contact

Tool to delete a contact from a brand in BigMailer.

Delete Custom Field

Deletes a custom field from a specified brand in BigMailer.

Delete List

Tool to delete a list from BigMailer.

Delete Segment

Tool to delete a segment from a brand in BigMailer.

Delete Template

Tool to delete a template from BigMailer.

Delete User

Tool to delete a user from BigMailer.

Get Brand

Tool to retrieve detailed information about a specific brand by its ID.

Get Brand Property

Tool to retrieve a specific brand property by its ID for a given brand.

Get Bulk Campaign

Tool to retrieve detailed information about a specific bulk campaign in BigMailer.

Get Contact

Tool to retrieve detailed information about a specific contact from BigMailer.

Get Contact Batch Status

Tool to retrieve the status and results of a contact batch upload in BigMailer.

Get Custom Field

Tool to retrieve a custom field from a BigMailer brand.

Get List

Tool to retrieve details of a specific list within a brand.

Get Segment

Tool to retrieve a specific segment from BigMailer by brand ID and segment ID.

Get Suppression List

Tool to retrieve details of a specific suppression list for a brand in BigMailer.

Get Template

Tool to retrieve detailed information about a specific template by its ID.

Get Transactional Campaign

Tool to retrieve detailed information about a specific transactional campaign in BigMailer.

Get User

Tool to retrieve detailed information about a specific user by their ID.

Get User Information

This tool retrieves information about the authenticated user in BigMailer using the GET /me endpoint.

List All Brands

This tool retrieves a list of all brands associated with the authenticated BigMailer account.

List Brand Properties

Tool to retrieve a list of brand properties for a specific brand in BigMailer.

List Bulk Campaigns

Tool to list bulk campaigns for a specified brand in BigMailer.

List Connections

Tool to list all connections in your BigMailer account.

List Contacts

Tool to list contacts for a brand in BigMailer.

List Fields

Tool to list custom fields for a brand in BigMailer.

List Contact Lists

Tool to retrieve all contact lists for a specified brand in BigMailer.

List Message Types

Tool to list message types for a specific brand in BigMailer.

List Segments

Tool to list segments for a brand in BigMailer.

List Senders

Tool to list all senders configured for a specific brand in BigMailer.

List Suppression Lists

Tool to list suppression lists for a specific brand.

List Templates

Tool to list templates for a brand in BigMailer.

List Transactional Campaigns

Tool to list transactional campaigns for a specified brand in BigMailer.

List Users

Tool to list all users in your BigMailer account.

Update Brand

Tool to update a brand in BigMailer.

Update Brand Property

Tool to update a brand property in BigMailer.

Update Bulk Campaign

Tool to update an existing bulk campaign in BigMailer.

Update Contact

Tool to update an existing contact in BigMailer.

Update Field

Tool to update a custom field in BigMailer.

Update List

Tool to update a list in BigMailer.

Update Segment

Tool to update an existing segment in BigMailer.

Update Template

Tool to update an existing email or page template in BigMailer.

Update Transactional Campaign

Tool to update a transactional campaign in BigMailer.

Update User

Tool to update a user in BigMailer.

Upsert Contact

Tool to create or update a contact in a BigMailer brand.

FAQ

Frequently asked questions

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

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

Start with Bigmailer.It takes 30 seconds.

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

Start building