How to integrate Dynosend MCP with Claude Code

Manage your Dynosend directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

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

Manage your Dynosend directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Dynosend with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Dynosend to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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.

Connecting Dynosend via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Dynosend) for even more tool search precision. It's secure and reliable.

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 step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Dynosend account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['dynosend'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http dynosend-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Dynosend. This URL will be used to connect Claude Code to Dynosend.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Dynosend
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Dynosend MCP to Claude Code

bash
claude mcp add --transport http dynosend-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (dynosend-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Dynosend MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your dynosend-composio entry in the list
  • This confirms that Claude Code can now access Dynosend tools

If everything is wired up, you should see your dynosend-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Dynosend

The first time you try to use Dynosend tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Dynosend
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Dynosend authorization flow
  • Return to the terminal and start using Dynosend through Claude Code

Once authenticated, you can ask Claude Code to perform Dynosend operations in natural language. For example:

  • "Add contact to newsletter audience"
  • "Summarize latest campaign engagement metrics"
  • "Track signup event for customer"

Complete Code

Here's the complete code to get you started with Dynosend and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['dynosend'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http dynosend-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Dynosend with Claude Code using Composio's MCP server. Now you can interact with Dynosend directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Dynosend operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Dynosend operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

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 Code 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