# How to integrate Omnisend MCP with Pydantic AI ```json { "title": "How to integrate Omnisend MCP with Pydantic AI", "toolkit": "Omnisend", "toolkit_slug": "omnisend", "framework": "Pydantic AI", "framework_slug": "pydantic-ai", "url": "https://composio.dev/toolkits/omnisend/framework/pydantic-ai", "markdown_url": "https://composio.dev/toolkits/omnisend/framework/pydantic-ai.md", "updated_at": "2026-05-12T10:20:31.368Z" } ``` ## Introduction This guide walks you through connecting Omnisend to Pydantic AI 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 Pydantic AI 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 - [OpenAI Agents SDK](https://composio.dev/toolkits/omnisend/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/omnisend/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/omnisend/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/omnisend/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/omnisend/framework/codex) - [OpenClaw](https://composio.dev/toolkits/omnisend/framework/openclaw) - [Hermes](https://composio.dev/toolkits/omnisend/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/omnisend/framework/cli) - [Google ADK](https://composio.dev/toolkits/omnisend/framework/google-adk) - [LangChain](https://composio.dev/toolkits/omnisend/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/omnisend/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/omnisend/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/omnisend/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/omnisend/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up your Composio API key and User ID - How to create a Composio Tool Router session for Omnisend - How to attach an MCP Server to a Pydantic AI agent - How to stream responses and maintain chat history - How to build a simple REPL-style chat interface to test your Omnisend workflows ## What is Pydantic AI? Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications. Key features include: - Type Safety: Built on Pydantic for automatic data validation - MCP Support: Native support for Model Context Protocol servers - Streaming: Built-in support for streaming responses - Async First: Designed for async/await patterns ## 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 | Tool slug | Name | Description | |---|---|---| | `OMNISEND_ADD_CART_PRODUCT` | Add Cart Product | Tool to add a product to a cart in Omnisend (v3 API). Use when updating cart contents or tracking abandoned carts. | | `OMNISEND_CREATE_BATCH` | Create Batch | Tool to create a new batch operation for multiple items. Use when you need to process many records asynchronously in one call, e.g., bulk contacts, products, orders, or events. Use after preparing the items list to avoid rate limits. | | `OMNISEND_CREATE_CART` | Create Cart | Tool to create a new shopping cart in Omnisend. Use when tracking customer cart activity for abandoned cart campaigns. | | `OMNISEND_CREATE_CATEGORY` | Create Category | Tool to create a new category in Omnisend. Use when organizing products into categories. | | `OMNISEND_CREATE_ORDER` | Create Order | Tool to create a new order in Omnisend v3 API. Use when recording a customer purchase or order transaction. | | `OMNISEND_CREATE_OR_UPDATE_CONTACT` | Create or Update Contact | Tool to create or update a contact in Omnisend. Use after collecting subscriber details. | | `OMNISEND_CREATE_PRODUCT` | Create Product | Tool to create a new product in the Omnisend product catalog. Use when adding products for email campaigns or syncing inventory. | | `OMNISEND_CREATE_PRODUCT_CATEGORY` | Create Product Category | Tool to create a new product category in the Omnisend catalog. Use when organizing products into categories. | | `OMNISEND_DELETE_CART` | Delete Cart | Tool to delete a cart from Omnisend by its ID (v3 API). Use when you need to remove an abandoned or expired cart from the system. | | `OMNISEND_DELETE_CATEGORY` | Delete Category | Tool to remove a category from Omnisend by its ID. Use when you need to delete a category and ensure it is no longer available in your catalog. | | `OMNISEND_DELETE_ORDER` | Delete Order | Tool to delete an order from Omnisend by its ID. Use when you need to remove an order from the system. | | `OMNISEND_DELETE_PRODUCT` | Delete Product | Tool to remove a product from Omnisend by its ID. Use when you need to delete a product and ensure it is no longer available in your catalog. | | `OMNISEND_DELETE_PRODUCT_CATEGORY` | Delete Product Category | Tool to remove a product category from Omnisend by its ID. Use when you need to delete a product category from your catalog. | | `OMNISEND_GET_BATCHES` | Get Batches | Tool to retrieve a list of batch operations. Use after initiating a batch job to monitor its progress and results. | | `OMNISEND_GET_BATCH_INFORMATION` | Get Batch Information | Tool to retrieve information about a specific batch by ID. Use after submitting a batch when you need a detailed status and counts. | | `OMNISEND_GET_BATCH_ITEM` | Get Batch Item | Tool to retrieve a specific item within a batch by batchID and itemID. Use when you need to inspect the result of a single batch operation. | | `OMNISEND_GET_BATCH_ITEMS` | Get Batch Items | Tool to retrieve processed items of a specific batch by ID. Use when you need to inspect individual results of a batch operation after fetching batch details. | | `OMNISEND_GET_BRAND` | Get Brand | Tool to retrieve information about the current authenticated brand. Use when you need brand details like currency, platform, or website. | | `OMNISEND_GET_CART` | Get Cart | Tool to retrieve a specific cart by ID from Omnisend v3 API. Use when you need detailed cart information including products and customer contact details. | | `OMNISEND_GET_CATEGORY` | Get Category | Tool to retrieve details of a specific category by ID. Use when you need to fetch information about a category. | | `OMNISEND_GET_CONTACT` | Get Contact | Tool to retrieve details of a single contact by ID. Use when you already have a contactId and need the full profile. | | `OMNISEND_GET_ORDER` | Get Order | Tool to retrieve details of a specific order by ID. Use when you need order information including products, addresses, and payment details. | | `OMNISEND_GET_PRODUCT` | Get Product | Tool to retrieve details of a specific product by ID from Omnisend. Use when you need full product information including variants, pricing, and stock status. | | `OMNISEND_GET_PRODUCT_CATEGORY` | Get Product Category | Tool to retrieve a specific product category by ID. Use when you need details about a particular product category. | | `OMNISEND_LIST_CAMPAIGNS` | List Campaigns | Tool to retrieve a paginated list of campaigns with optional filtering by status and type. Use when you need to view or analyze campaign performance across multiple campaigns. | | `OMNISEND_LIST_CARTS` | List Carts | Tool to retrieve a paginated list of carts with optional filtering. Use when you need to fetch carts by date range, contact, or segment. | | `OMNISEND_LIST_CATEGORIES` | List Categories | Tool to retrieve a paginated list of product categories. Use when you need category IDs for product management or catalog organization. | | `OMNISEND_LIST_CONTACTS` | List Contacts | Tool to retrieve a paginated list of contacts with optional filtering. Use when you need to fetch contacts in batches and handle cursor pagination. | | `OMNISEND_LIST_EVENTS` | List Events | Tool to retrieve all custom events created in Omnisend app. Use when you need to view available event types for automation workflows or event tracking. | | `OMNISEND_LIST_PRODUCT_CATEGORIES` | List Product Categories | Tool to retrieve a paginated list of product categories from the Omnisend catalog. Use when fetching category data for product organization. | | `OMNISEND_LIST_PRODUCTS` | List Products | Tool to retrieve a paginated list of products. Use when syncing product catalog before campaign creation. | | `OMNISEND_REMOVE_CART_PRODUCT` | Remove Cart Product | Tool to remove a product from a cart in Omnisend. Use when you need to delete a specific product from a cart. | | `OMNISEND_REPLACE_CART` | Replace Cart | Tool to replace an existing cart in Omnisend using the v3 API. Use when you need to completely replace all cart data including products, pricing, and recovery URL. | | `OMNISEND_REPLACE_CART_PRODUCT` | Replace Cart Product | Tool to replace a product in a cart using Omnisend v3 API. Use when you need to update all details of a specific product in a cart. | | `OMNISEND_REPLACE_CATEGORY` | Replace Category | Tool to replace a category's title by ID. Use when you need to update an entire category resource. | | `OMNISEND_REPLACE_ORDER` | Replace Order | Tool to completely replace an existing order in Omnisend. Use when you need to update all order details at once, replacing the entire order record. | | `OMNISEND_REPLACE_PRODUCT` | Replace Product | Tool to replace an existing product in the Omnisend catalog. Use when you need to completely replace all product data with new information. | | `OMNISEND_SEND_EVENT` | Send Event | Tool to send a customer event to Omnisend. Events can trigger automations and track customer behavior. Use when you need to record customer interactions such as product views, cart actions, or custom events. | | `OMNISEND_UPDATE_CART` | Update Cart | Tool to partially update a cart in Omnisend (v3 API). Use when you need to modify cart details such as currency, total amount, recovery URL, or products. | | `OMNISEND_UPDATE_CART_PRODUCT` | Update Cart Product | Tool to update a product in a cart (v3 API). Use when you need to modify product details such as quantity, price, or other attributes for an existing cart item. | | `OMNISEND_UPDATE_CONTACT` | Update Contact | Tool to update fields of an existing contact by ID. Use after retrieving contact ID. PATCH https://api.omnisend.com/v3/contacts/{contactId} Example: UpdateContact(contactId="..., body={firstName: 'John'}) | | `OMNISEND_UPDATE_ORDER_STATUS` | Update Order Status | Tool to partially update an order status in Omnisend (v3 API). Use when you need to update shipping details, payment status, or fulfillment status of an existing order. | | `OMNISEND_UPDATE_PRODUCT_CATEGORY` | Update Product Category | Tool to update an existing product category title in Omnisend. Use when you need to modify a category's name. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Omnisend MCP server is an implementation of the Model Context Protocol that connects your AI agent to Omnisend. It provides structured and secure access so your agent can perform Omnisend operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Python 3.9 or higher - A Composio account with an active API key - Basic familiarity with Python and async programming ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies Install the required libraries. What's happening: - composio connects your agent to external SaaS tools like Omnisend - pydantic-ai lets you create structured AI agents with tool support - python-dotenv loads your environment variables securely from a .env file ```bash pip install composio pydantic-ai python-dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates your agent to Composio's API - USER_ID associates your session with your account for secure tool access - OPENAI_API_KEY to access OpenAI LLMs ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key ``` ### 4. Import dependencies What's happening: - We load environment variables and import required modules - Composio manages connections to Omnisend - MCPServerStreamableHTTP connects to the Omnisend MCP server endpoint - Agent from Pydantic AI lets you define and run the AI assistant ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from pydantic_ai import Agent from pydantic_ai.mcp import MCPServerStreamableHTTP load_dotenv() ``` ### 5. Create a Tool Router Session What's happening: - We're creating a Tool Router session that gives your agent access to Omnisend tools - The create method takes the user ID and specifies which toolkits should be available - The returned session.mcp.url is the MCP server URL that your agent will use ```python async def main(): api_key = os.getenv("COMPOSIO_API_KEY") user_id = os.getenv("USER_ID") if not api_key or not user_id: raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment") # Create a Composio Tool Router session for Omnisend composio = Composio(api_key=api_key) session = composio.create( user_id=user_id, toolkits=["omnisend"], ) url = session.mcp.url if not url: raise ValueError("Composio session did not return an MCP URL") ``` ### 6. Initialize the Pydantic AI Agent What's happening: - The MCP client connects to the Omnisend endpoint - The agent uses GPT-5 to interpret user commands and perform Omnisend operations - The instructions field defines the agent's role and behavior ```python # Attach the MCP server to a Pydantic AI Agent omnisend_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY}) agent = Agent( "openai:gpt-5", toolsets=[omnisend_mcp], instructions=( "You are a Omnisend assistant. Use Omnisend tools to help users " "with their requests. Ask clarifying questions when needed." ), ) ``` ### 7. Build the chat interface What's happening: - The agent reads input from the terminal and streams its response - Omnisend API calls happen automatically under the hood - The model keeps conversation history to maintain context across turns ```python # Simple REPL with message history history = [] print("Chat started! Type 'exit' or 'quit' to end.\n") print("Try asking the agent to help you with Omnisend.\n") while True: user_input = input("You: ").strip() if user_input.lower() in {"exit", "quit", "bye"}: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n", flush=True) async with agent.run_stream(user_input, message_history=history) as stream_result: collected_text = "" async for chunk in stream_result.stream_output(): text_piece = None if isinstance(chunk, str): text_piece = chunk elif hasattr(chunk, "delta") and isinstance(chunk.delta, str): text_piece = chunk.delta elif hasattr(chunk, "text"): text_piece = chunk.text if text_piece: collected_text += text_piece result = stream_result print(f"Agent: {collected_text}\n") history = result.all_messages() ``` ### 8. Run the application What's happening: - The asyncio loop launches the agent and keeps it running until you exit ```python if __name__ == "__main__": asyncio.run(main()) ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from pydantic_ai import Agent from pydantic_ai.mcp import MCPServerStreamableHTTP load_dotenv() async def main(): api_key = os.getenv("COMPOSIO_API_KEY") user_id = os.getenv("USER_ID") if not api_key or not user_id: raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment") # Create a Composio Tool Router session for Omnisend composio = Composio(api_key=api_key) session = composio.create( user_id=user_id, toolkits=["omnisend"], ) url = session.mcp.url if not url: raise ValueError("Composio session did not return an MCP URL") # Attach the MCP server to a Pydantic AI Agent omnisend_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY}) agent = Agent( "openai:gpt-5", toolsets=[omnisend_mcp], instructions=( "You are a Omnisend assistant. Use Omnisend tools to help users " "with their requests. Ask clarifying questions when needed." ), ) # Simple REPL with message history history = [] print("Chat started! Type 'exit' or 'quit' to end.\n") print("Try asking the agent to help you with Omnisend.\n") while True: user_input = input("You: ").strip() if user_input.lower() in {"exit", "quit", "bye"}: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n", flush=True) async with agent.run_stream(user_input, message_history=history) as stream_result: collected_text = "" async for chunk in stream_result.stream_output(): text_piece = None if isinstance(chunk, str): text_piece = chunk elif hasattr(chunk, "delta") and isinstance(chunk.delta, str): text_piece = chunk.delta elif hasattr(chunk, "text"): text_piece = chunk.text if text_piece: collected_text += text_piece result = stream_result print(f"Agent: {collected_text}\n") history = result.all_messages() if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You've built a Pydantic AI agent that can interact with Omnisend through Composio's Tool Router. With this setup, your agent can perform real Omnisend actions through natural language. You can extend this further by: - Adding other toolkits like Gmail, HubSpot, or Salesforce - Building a web-based chat interface around this agent - Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Omnisend for workflow automation) This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations. ## How to build Omnisend MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/omnisend/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/omnisend/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/omnisend/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/omnisend/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/omnisend/framework/codex) - [OpenClaw](https://composio.dev/toolkits/omnisend/framework/openclaw) - [Hermes](https://composio.dev/toolkits/omnisend/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/omnisend/framework/cli) - [Google ADK](https://composio.dev/toolkits/omnisend/framework/google-adk) - [LangChain](https://composio.dev/toolkits/omnisend/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/omnisend/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/omnisend/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/omnisend/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/omnisend/framework/crew-ai) ## Related Toolkits - [Reddit](https://composio.dev/toolkits/reddit) - Reddit is a social news platform with thriving user-driven communities (subreddits). It's the go-to place for discussion, content sharing, and viral marketing. - [Facebook](https://composio.dev/toolkits/facebook) - Facebook is a social media and advertising platform for businesses and creators. It helps you connect, share, and manage content across your public Facebook Pages. - [Linkedin](https://composio.dev/toolkits/linkedin) - LinkedIn is a professional networking platform for connecting, sharing content, and engaging with business opportunities. It's the go-to place for building your professional brand and unlocking new career connections. - [Active campaign](https://composio.dev/toolkits/active_campaign) - ActiveCampaign is a marketing automation and CRM platform for managing email campaigns, sales pipelines, and customer segmentation. It helps businesses engage customers and drive growth through smart automation and targeted outreach. - [ActiveTrail](https://composio.dev/toolkits/active_trail) - ActiveTrail is a user-friendly email marketing and automation platform. It helps you reach subscribers and automate campaigns with ease. - [Ahrefs](https://composio.dev/toolkits/ahrefs) - Ahrefs is an SEO and marketing platform for site audits, keyword research, and competitor insights. It helps you improve search rankings and drive organic traffic. - [Amcards](https://composio.dev/toolkits/amcards) - AMCards lets you create and mail personalized greeting cards online. Build stronger customer relationships with easy, automated card campaigns. - [Beamer](https://composio.dev/toolkits/beamer) - Beamer is a news and changelog platform for in-app announcements and feature updates. It helps companies boost user engagement by sharing news where users are most active. - [Benchmark email](https://composio.dev/toolkits/benchmark_email) - Benchmark Email is a platform for creating, sending, and tracking email campaigns. It's built to help you engage audiences and analyze results—all in one place. - [Bigmailer](https://composio.dev/toolkits/bigmailer) - 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. - [Brandfetch](https://composio.dev/toolkits/brandfetch) - Brandfetch is an API that delivers company logos, colors, and visual branding assets. It helps marketers and developers keep brand visuals consistent everywhere. - [Brevo](https://composio.dev/toolkits/brevo) - 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. - [Campayn](https://composio.dev/toolkits/campayn) - Campayn is an email marketing platform for creating, sending, and managing campaigns. It helps businesses engage contacts and grow audiences with easy-to-use tools. - [Cardly](https://composio.dev/toolkits/cardly) - Cardly is a platform for creating and sending personalized direct mail to customers. It helps businesses break through the digital clutter by getting real engagement via physical mailboxes. - [ClickSend](https://composio.dev/toolkits/clicksend) - ClickSend is a cloud-based SMS and email marketing platform for businesses. It streamlines communication by enabling quick message delivery and contact management. - [Crustdata](https://composio.dev/toolkits/crustdata) - CrustData is an AI-powered data intelligence platform for real-time company and people data. It helps B2B sales teams, AI SDRs, and investors react to live business signals. - [Curated](https://composio.dev/toolkits/curated) - Curated is a platform for collecting, curating, and publishing newsletters. It streamlines content aggregation and distribution for creators and teams. - [Customerio](https://composio.dev/toolkits/customerio) - Customer.io is a customer engagement platform for targeted messaging across email, SMS, and push. Easily automate, segment, and track communications with your audience. - [Cutt ly](https://composio.dev/toolkits/cutt_ly) - Cutt.ly is a URL shortening service for managing and analyzing links. Streamline your workflows with quick, trackable, and branded short URLs. - [Demio](https://composio.dev/toolkits/demio) - Demio is webinar software built for marketers, offering both live and automated sessions with interactive features. It helps teams engage audiences and optimize lead generation through detailed analytics. ## Frequently Asked Questions ### 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 Pydantic AI? Yes, you can. Pydantic AI 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. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)