How to integrate Omnisend MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Omnisend logo
Claude Agent SDK logo
divider

Introduction

This guide walks you through connecting Omnisend to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Omnisend agent that can add new subscribers from latest signups, update contact email preferences in bulk, list all products for upcoming campaign through natural language commands.

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

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

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

The Omnisend MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Omnisend account. It provides structured and secure access to your ecommerce marketing data, so your agent can manage contacts, automate batch operations, update products, and streamline campaign preparation for your store.

  • Bulk contact and product management: Effortlessly create or update large sets of contacts or products in one go, perfect for onboarding new subscribers or syncing your catalog.
  • Individual contact handling: Retrieve, update, or enrich detailed contact profiles, making it easy for your agent to personalize outreach or manage subscriptions.
  • Batch job automation and tracking: Initiate batch operations and monitor their progress, status, and results to ensure smooth processing of large datasets.
  • Product catalog maintenance: List, review, or delete products directly from your Omnisend account, keeping your store's offerings up to date for campaigns.
  • Contact segmentation and filtering: Fetch paginated and filtered contact lists, enabling targeted marketing actions and smarter audience management.

Supported Tools & Triggers

Tools
Add Cart ProductTool to add a product to a cart in Omnisend (v3 API).
Create BatchTool to create a new batch operation for multiple items.
Create CartTool to create a new shopping cart in Omnisend.
Create CategoryTool to create a new category in Omnisend.
Create OrderTool to create a new order in Omnisend v3 API.
Create or Update ContactTool to create or update a contact in Omnisend.
Create ProductTool to create a new product in the Omnisend product catalog.
Create Product CategoryTool to create a new product category in the Omnisend catalog.
Delete CartTool to delete a cart from Omnisend by its ID (v3 API).
Delete CategoryTool to remove a category from Omnisend by its ID.
Delete OrderTool to delete an order from Omnisend by its ID.
Delete ProductTool to remove a product from Omnisend by its ID.
Delete Product CategoryTool to remove a product category from Omnisend by its ID.
Get BatchesTool to retrieve a list of batch operations.
Get Batch InformationTool to retrieve information about a specific batch by ID.
Get Batch ItemTool to retrieve a specific item within a batch by batchID and itemID.
Get Batch ItemsTool to retrieve processed items of a specific batch by ID.
Get BrandTool to retrieve information about the current authenticated brand.
Get CartTool to retrieve a specific cart by ID from Omnisend v3 API.
Get CategoryTool to retrieve details of a specific category by ID.
Get ContactTool to retrieve details of a single contact by ID.
Get OrderTool to retrieve details of a specific order by ID.
Get ProductTool to retrieve details of a specific product by ID from Omnisend.
Get Product CategoryTool to retrieve a specific product category by ID.
List CampaignsTool to retrieve a paginated list of campaigns with optional filtering by status and type.
List CartsTool to retrieve a paginated list of carts with optional filtering.
List CategoriesTool to retrieve a paginated list of product categories.
List ContactsTool to retrieve a paginated list of contacts with optional filtering.
List EventsTool to retrieve all custom events created in Omnisend app.
List Product CategoriesTool to retrieve a paginated list of product categories from the Omnisend catalog.
List ProductsTool to retrieve a paginated list of products.
Remove Cart ProductTool to remove a product from a cart in Omnisend.
Replace CartTool to replace an existing cart in Omnisend using the v3 API.
Replace Cart ProductTool to replace a product in a cart using Omnisend v3 API.
Replace CategoryTool to replace a category's title by ID.
Replace OrderTool to completely replace an existing order in Omnisend.
Replace ProductTool to replace an existing product in the Omnisend catalog.
Send EventTool to send a customer event to Omnisend.
Update CartTool to partially update a cart in Omnisend (v3 API).
Update Cart ProductTool to update a product in a cart (v3 API).
Update ContactTool to update fields of an existing contact by ID.
Update Order StatusTool to partially update an order status in Omnisend (v3 API).
Update Product CategoryTool to update an existing product category title in Omnisend.

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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Omnisend account
  • Some knowledge of Python

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.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

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

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Omnisend functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Omnisend
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["omnisend"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
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 Omnisend
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Omnisend tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Omnisend
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Omnisend and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Omnisend
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["omnisend"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Omnisend tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Omnisend 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.

How to build Omnisend MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Omnisend MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Omnisend MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Omnisend MCP with Claude Cowork

Codex logo

Codex

Use Omnisend MCP with Codex

OpenClaw logo

OpenClaw

Use Omnisend MCP with OpenClaw

Hermes logo

Hermes

Use Omnisend MCP with Hermes

CLI logo

CLI

Use Omnisend MCP with CLI

Google ADK logo

Google ADK

Use Omnisend MCP with Google ADK

LangChain logo

LangChain

Use Omnisend MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Omnisend MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Omnisend MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Omnisend MCP with LlamaIndex

CrewAI logo

CrewAI

Use Omnisend MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Omnisend MCP?

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

Can I use Tool Router MCP with Claude Agent SDK?

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

Can I manage the permissions and scopes for Omnisend while using Tool Router?

Yes, absolutely. You can configure which Omnisend 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.

How safe is my data with Composio Tool Router?

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 Omnisend data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗