How to integrate Dynosend MCP with Claude Agent SDK

This guide walks you through connecting Dynosend to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Dynosend agent that can add contact to newsletter audience, summarize latest campaign engagement metrics, track signup event for customer through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Dynosend account through Composio's Dynosend MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Dynosend logoDynosend
Api Key

Dynosend is an email marketing platform for audiences, contacts, campaigns, transactional messages, and customer events. Use it to manage lifecycle email, track engagement, and keep customer communication organized.

18 Tools

Introduction

This guide walks you through connecting Dynosend to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Dynosend agent that can add contact to newsletter audience, summarize latest campaign engagement metrics, track signup event for customer through natural language commands.

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

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

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

The Dynosend MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dynosend account. It provides structured and secure access to your audiences, contacts, campaigns, transactional messages, and customer events, so your agent can manage contacts, operate campaigns, send transactional messages, track customer activity, and maintain your blacklist on your behalf.

  • Audience and contact management: Have your agent list audiences, create or update contacts, manage tags and custom fields, find duplicate contacts, and delete contacts when required for privacy compliance.
  • Subscription and blacklist control: Let the agent subscribe or unsubscribe contacts, check whether an email is blacklisted, and add addresses to the blacklist when needed.
  • Campaign operations and insights: Direct your agent to list campaigns, review delivery and engagement results, start ready campaigns, or pause and resume campaign delivery.
  • Transactional email delivery: Instruct your agent to send configured transactional messages through your Dynosend account.
  • Customer event tracking: Have your agent record application events for contacts to keep customer activity available in Dynosend.

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

Add Email To Blacklist

Permanently add an email address to the Dynosend blacklist.

Add Tags To Contact

Append one or more tags to a contact without replacing its existing tags.

Check Blacklist

Check whether an email address is on the connected Dynosend account's blacklist and return its timestamp and reason when available.

Create Contact

Create a contact in an audience, optionally assigning tags and audience-defined custom fields.

Delete Contact

Permanently delete one contact from an audience for GDPR/CCPA erasure.

Find Duplicate Contacts

Find contacts that use the same email address across all audiences in the connected Dynosend account.

Get Audience

Get one audience's configuration, custom-field definitions, contact information, and subscription statistics by audience UID.

Get Campaign

Get one campaign's configuration and delivery, open, click, spam, bounce, and unsubscribe insights.

Get Contact

Get one contact in an audience by contact UID or email address.

List Audiences

List audiences available to the connected Dynosend account, including the UID needed by audience and contact tools.

List Campaigns

List campaigns in the connected Dynosend account, including status and the campaign UID used by campaign tools.

List Contacts

Return one page of contacts in a Dynosend audience, including contact UIDs, subscription status, tags, and audience-defined custom-field values.

Record Contact Event

Record an application event for a contact in an audience.

Send Transactional Message

Send a configured Dynosend transactional message.

Set Campaign Delivery State

Pause a sending campaign or resume a paused campaign by setting its delivery state to paused or sending.

Set Contact Subscription Status

Set a contact's subscription status to subscribed or unsubscribed in an audience.

Start Campaign

Start a ready broadcast campaign.

Update Contact

Update a contact's email, replace its complete tag set, or set audience-defined custom fields.

FAQ

Frequently asked questions

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

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

Start with Dynosend.It takes 30 seconds.

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

Start building