How to integrate Brevo MCP with Claude Agent SDK

This guide walks you through connecting Brevo to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Brevo agent that can send sms campaign to new subscribers, create or update an email template, find contact details by email address through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Brevo account through Composio's Brevo MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Brevo logoBrevo
Api KeyOauth2

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.

21 Tools

Introduction

This guide walks you through connecting Brevo to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Brevo agent that can send sms campaign to new subscribers, create or update an email template, find contact details by email address through natural language commands.

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

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

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

The Brevo MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Brevo account. It provides structured and secure access to your email, SMS marketing, automation, and contact management tools, so your agent can perform actions like sending campaigns, managing contacts, creating templates, and retrieving account details on your behalf.

  • Automated campaign management: Let your agent create, schedule, or delete SMS campaigns, including customizing recipients, sender details, and campaign content.
  • Contact and company management: Easily add new contacts or companies, update existing records, or remove outdated ones to keep your database organized and up to date.
  • Email template automation: Empower your agent to create, update, or delete email templates for consistent and efficient campaign design and execution.
  • Account information retrieval: Ask your agent to fetch detailed account information, including plan details, credits, and profile data, for easy monitoring and reporting.
  • Contact search and segmentation: Have your agent search for specific contacts or retrieve segmented contact lists based on filters like creation date, list IDs, or attributes.

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

Create a company

Creates a new company record in your Brevo CRM.

Create Contact List

Creates a new contact list (audience) in Brevo within a specified folder.

Create or Update Email Template

This tool creates a new email template or updates an existing one in Brevo.

Create SMS Campaign

This tool allows you to create a new SMS campaign in Brevo.

Delete a company

Deletes a company from Brevo using its unique identifier.

Delete Contact

Deletes a contact from Brevo by email, contact ID, external ID, phone number, WhatsApp ID, or landline number.

Delete Email Template

This tool deletes an inactive email template from Brevo.

Delete SMS Campaign

This tool deletes an existing SMS campaign.

Get Account Information

Retrieves comprehensive information about the authenticated Brevo account.

Get all contacts

This tool retrieves all contacts from your Brevo account with pagination and filtering based on modification/creation dates, list IDs, segment IDs, and contact attributes.

Get all email templates

This tool retrieves a list of all email templates created in your Brevo account.

Get All Senders

This tool retrieves a list of all senders associated with the Brevo account.

Get Company Details

Retrieves detailed information about a specific company from Brevo's CRM.

Get Contact Details

This tool retrieves detailed information about a specific contact in Brevo.

Get contact lists

Retrieves all contact lists from your Brevo account with pagination support.

Get Email Campaign Details

Tool to retrieve full configuration and content for a specific email campaign.

Get SMS Campaign Details

Retrieves the details of a specific SMS campaign.

Get SMS Campaigns

Retrieves all SMS campaigns from your Brevo account with optional filtering and pagination.

List All Companies

This action retrieves a list of all companies stored in the Brevo CRM.

List Email Campaigns

This tool retrieves a list of all email campaigns associated with the user's Brevo account.

Update Email Campaign

Updates an email campaign in Brevo using its unique identifier.

FAQ

Frequently asked questions

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

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

Start with Brevo.It takes 30 seconds.

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

Start building