# How to integrate Svix MCP with Autogen ```json { "title": "How to integrate Svix MCP with Autogen", "toolkit": "Svix", "toolkit_slug": "svix", "framework": "AutoGen", "framework_slug": "autogen", "url": "https://composio.dev/toolkits/svix/framework/autogen", "markdown_url": "https://composio.dev/toolkits/svix/framework/autogen.md", "updated_at": "2026-05-12T10:27:41.825Z" } ``` ## Introduction This guide walks you through connecting Svix to AutoGen using the Composio tool router. By the end, you'll have a working Svix agent that can list all webhook endpoints for app x, create a new webhook endpoint for payments, update application rate limit to 1000/min through natural language commands. This guide will help you understand how to give your AutoGen agent real control over a Svix account through Composio's Svix MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Svix with - [OpenAI Agents SDK](https://composio.dev/toolkits/svix/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/svix/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/svix/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/svix/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/svix/framework/codex) - [OpenClaw](https://composio.dev/toolkits/svix/framework/openclaw) - [Hermes](https://composio.dev/toolkits/svix/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/svix/framework/cli) - [Google ADK](https://composio.dev/toolkits/svix/framework/google-adk) - [LangChain](https://composio.dev/toolkits/svix/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/svix/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/svix/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/svix/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/svix/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get and set up your OpenAI and Composio API keys - Install the required dependencies for Autogen and Composio - Initialize Composio and create a Tool Router session for Svix - Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams - Configure an Autogen AssistantAgent that can call Svix tools - Run a live chat loop where you ask the agent to perform Svix operations ## What is AutoGen? Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows. Key features include: - Multi-Agent Systems: Build collaborative agent workflows - MCP Workbench: Native support for Model Context Protocol tools - Streaming HTTP: Connect to external services through streamable HTTP - AssistantAgent: Pre-built agent class for tool-using assistants ## What is the Svix MCP server, and what's possible with it? The Svix MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Svix account. It provides structured and secure access to your webhooks infrastructure, so your agent can perform actions like managing applications, configuring endpoints, sending webhooks, and monitoring delivery attempts on your behalf. - Application management and automation: Ask your agent to create, update, list, or delete Svix applications, making it easy to manage webhook-enabled projects programmatically. - Endpoint configuration: Have your agent register, retrieve, or remove webhook endpoints for your applications, ensuring your events get delivered to the right places. - Webhook delivery tracking: Let your agent fetch detailed information about message delivery attempts, helping you monitor reliability and debug failed webhooks with ease. - Comprehensive application insights: Retrieve metadata and details for any Svix application, so your agent can surface key info or audit your webhook ecosystem. - Automated cleanup and maintenance: Direct your agent to delete outdated applications or endpoints, streamlining your webhook management and reducing clutter. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `SVIX_APP_CREATE` | Create Application | Tool to create a new Svix application. Use when you need to register an application with specific settings. | | `SVIX_APP_DELETE` | Delete Svix Application | Permanently delete a Svix application by its ID or UID. Use this to remove an application and all its associated endpoints, messages, and webhooks. This action is destructive and cannot be undone. | | `SVIX_APP_GET` | Get Application | Tool to retrieve details of a specific Svix application by its ID. Use when you need application metadata after authenticating with Svix. | | `SVIX_APP_LIST` | List Applications | Tool to list all applications. Use when you need to retrieve or paginate through your Svix applications. | | `SVIX_APP_UPDATE` | Update Svix Application | Tool to update an existing Svix application by ID. Use when you need to modify properties like name, rate limit, UID, or metadata. Call after confirming the correct app_id. | | `SVIX_ATTEMPT_GET` | Get Attempt Details | Tool to retrieve details of a specific message attempt. Use after confirming app_id, msg_id, and attempt_id. | | `SVIX_ATTEMPT_LIST` | List Message Attempts | Tool to list all delivery attempts for a specific message. Use after confirming message ID to debug attempts. | | `SVIX_ENDPOINT_CREATE` | Create Endpoint | Tool to create a new Svix webhook endpoint. Use after obtaining the app ID to register your webhook receiver URL. | | `SVIX_ENDPOINT_DELETE` | Delete Endpoint | Tool to delete an endpoint. Use when you need to remove a specific endpoint after confirming its application and endpoint IDs. | | `SVIX_ENDPOINT_GET` | Get Endpoint | Tool to retrieve details of a specific endpoint. Use after confirming app_id and endpoint_id. | | `SVIX_ENDPOINT_LIST` | List Endpoints | Tool to list all endpoints for a specific application. Use after obtaining the application ID to retrieve its endpoints. | | `SVIX_ENDPOINT_PATCH` | Patch Endpoint | Tool to partially update an endpoint’s configuration. Use when you need to adjust endpoint settings without full replacement. | | `SVIX_ENDPOINT_PATCH_HEADERS` | Patch Endpoint Headers | Tool to partially update headers for a specific endpoint. Use when you need to add, modify, or remove custom headers after endpoint creation. | | `SVIX_ENDPOINT_RECOVER_FAILED_WEBHOOKS` | Recover Failed Webhooks | Tool to recover messages that failed to send to an endpoint. Use when you need to retry webhook delivery for failed events after identifying delivery failures. | | `SVIX_ENDPOINT_REPLAY_MISSING` | Replay Missing Webhooks | Tool to replay missing webhooks for a specific endpoint. Use when some webhooks failed or were lost and need to be resent. | | `SVIX_ENDPOINT_SECRET_GET` | Get Endpoint Secret | Tool to retrieve the secret for a specific endpoint. Use after confirming app_id and endpoint_id. | | `SVIX_ENDPOINT_SECRET_ROTATE` | Rotate Endpoint Secret | Tool to rotate the signing secret key for an endpoint. Use when you need to invalidate the current secret and generate or supply a new one. Call after confirming app_id and endpoint_id. | | `SVIX_ENDPOINT_SEND_EXAMPLE_MESSAGE` | Send Example Message | Tool to send a test message for a specific event type to an endpoint. Use after setting up an endpoint to verify its configuration. Note: the endpoint's filter_types must include the event_type being tested; otherwise real events will not be delivered even if the example message sends successfully. | | `SVIX_ENDPOINT_STATS_GET` | Get Endpoint Stats | Tool to retrieve basic statistics for a specific endpoint. Use after confirming app_id and endpoint_id. | | `SVIX_ENDPOINT_TRANSFORMATION_GET` | Get Endpoint Transformation | Tool to retrieve transformation settings for a specific endpoint. Use after confirming app_id and endpoint_id. | | `SVIX_ENDPOINT_TRANSFORMATION_SET` | Set Endpoint Transformation | Tool to set or update transformation settings for an endpoint. Use when you need to configure or toggle an endpoint's transformation code after creation. | | `SVIX_ENDPOINT_UPDATE` | Update Endpoint | Tool to update an existing endpoint or create it if it doesn't exist (upsert). Use when you need to modify endpoint settings like URL, rate limit, channels, or metadata. If the endpoint doesn't exist, a new one will be created with the specified endpoint_id as its uid. | | `SVIX_ENDPOINT_UPDATE_HEADERS` | Update Endpoint Headers | Tool to completely replace headers for a specific endpoint. Use when you need to set a full new header mapping. | | `SVIX_EVENT_TYPE_CREATE` | Create Event Type | Create a new event type in Svix or unarchive an existing one. Event types are identifiers (like 'order.created', 'user.signup') that categorize the webhooks your application sends. Use period-delimited naming to group related events. Both 'name' and 'description' are required. Returns HTTP 409 if the event type already exists. | | `SVIX_EVENT_TYPE_DELETE` | Delete Event Type | Tool to delete an event type. Use when you need to archive or permanently expunge a specific event type after confirming its name. | | `SVIX_EVENT_TYPE_GET` | Get Event Type | Retrieve details of a specific event type by its name. Use this to inspect an existing event type's configuration, schema, and status. Event types define the categories of events that can be sent through Svix webhooks. | | `SVIX_EVENT_TYPE_LIST` | List Event Types | Tool to retrieve a list of all event types. Use when you need to inspect available event types, optionally including their JSON schemas. Use after authenticating the client. | | `SVIX_EVENT_TYPE_UPDATE` | Update Event Type | Update an existing event type's description, schema, feature flags, or archive status. Use this to modify event type configuration. The event type must already exist - use List Event Types or Get Event Type to find valid event type names. | | `SVIX_INTEGRATION_CREATE` | Create Integration | Tool to create a new integration for a specific application. Use after confirming the application ID. | | `SVIX_INTEGRATION_DELETE` | Delete Integration | Permanently delete an integration from a Svix application. This is a destructive operation that cannot be undone. Use when removing webhook integrations that are no longer needed. Requires both the application ID and the integration ID. Use 'List Integrations' first if you need to find the integration_id. | | `SVIX_INTEGRATION_GET` | Get Integration | Tool to retrieve details of a specific integration. Use after confirming app_id and integration_id. | | `SVIX_INTEGRATION_LIST` | List Integrations | Tool to list all integrations for a specific application. Use after confirming the application ID, supporting pagination via limit and iterator. Use when you need to enumerate integrations. | | `SVIX_INTEGRATION_UPDATE` | Update Integration | Tool to update an existing integration by ID. Use when you need to modify an integration's name or feature flags. | | `SVIX_MESSAGE_CREATE` | Create Message | Tool to create a new message for a specific application in Svix. Use after confirming app ID and event details. | | `SVIX_MESSAGE_GET` | Get Message | Tool to retrieve details of a specific message by its ID. Use when you need message metadata and status after dispatch. | | `SVIX_MESSAGE_LIST` | List Messages | Tool to list all messages for a specific application. Use when you need to fetch or paginate messages after obtaining the application ID. | | `SVIX_SOURCE_CREATE` | Create Source | Creates a new Svix Ingest source for receiving webhooks from external providers. A source generates an ingest URL that you can share with a webhook provider (e.g., GitHub, Stripe) as the destination for their webhooks. Svix will verify signatures based on the source type and forward the webhooks to your configured endpoints. Use 'genericWebhook' type to skip signature verification for providers not natively supported. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Svix MCP server is an implementation of the Model Context Protocol that connects your AI agents and assistants directly to Svix. Instead of manually wiring Svix APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely. 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 You will need: - A Composio API key - An OpenAI API key (used by Autogen's OpenAIChatCompletionClient) - A Svix account you can connect to Composio - Some basic familiarity with Autogen and Python async ### 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 Composio, Autogen extensions, and dotenv. What's happening: - composio connects your agent to Svix via MCP - autogen-agentchat provides the AssistantAgent class - autogen-ext-openai provides the OpenAI model client - autogen-ext-tools provides MCP workbench support ```bash pip install composio python-dotenv pip install autogen-agentchat autogen-ext-openai autogen-ext-tools ``` ### 3. Set up environment variables Create a .env file in your project folder. What's happening: - COMPOSIO_API_KEY is required to talk to Composio - OPENAI_API_KEY is used by Autogen's OpenAI client - USER_ID is how Composio identifies which user's Svix connections to use ```bash COMPOSIO_API_KEY=your-composio-api-key OPENAI_API_KEY=your-openai-api-key USER_ID=your-user-identifier@example.com ``` ### 4. Import dependencies and create Tool Router session What's happening: - load_dotenv() reads your .env file - Composio(api_key=...) initializes the SDK - create(...) creates a Tool Router session that exposes Svix tools - session.mcp.url is the MCP endpoint that Autogen will connect to ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Svix session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["svix"] ) url = session.mcp.url ``` ### 5. Configure MCP parameters for Autogen Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for. What's happening: - url points to the Tool Router MCP endpoint from Composio - timeout is the HTTP timeout for requests - sse_read_timeout controls how long to wait when streaming responses - terminate_on_close=True cleans up the MCP server process when the workbench is closed ```python # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) ``` ### 6. Create the model client and agent What's happening: - OpenAIChatCompletionClient wraps the OpenAI model for Autogen - McpWorkbench connects the agent to the MCP tools - AssistantAgent is configured with the Svix tools from the workbench ```python # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Svix assistant agent with MCP tools agent = AssistantAgent( name="svix_assistant", description="An AI assistant that helps with Svix operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) ``` ### 7. Run the interactive chat loop What's happening: - The script prompts you in a loop with You: - Autogen passes your input to the model, which decides which Svix tools to call via MCP - agent.run_stream(...) yields streaming messages as the agent thinks and calls tools - Typing exit, quit, or bye ends the loop ```python print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Svix related question or task to the agent.\n") # Conversation loop 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") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, "content") and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Svix session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["svix"] ) url = session.mcp.url # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Svix assistant agent with MCP tools agent = AssistantAgent( name="svix_assistant", description="An AI assistant that helps with Svix operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Svix related question or task to the agent.\n") # Conversation loop 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") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, 'content') and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You now have an Autogen assistant wired into Svix through Composio's Tool Router and MCP. From here you can: - Add more toolkits to the toolkits list, for example notion or hubspot - Refine the agent description to point it at specific workflows - Wrap this script behind a UI, Slack bot, or internal tool Once the pattern is clear for Svix, you can reuse the same structure for other MCP-enabled apps with minimal code changes. ## How to build Svix MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/svix/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/svix/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/svix/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/svix/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/svix/framework/codex) - [OpenClaw](https://composio.dev/toolkits/svix/framework/openclaw) - [Hermes](https://composio.dev/toolkits/svix/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/svix/framework/cli) - [Google ADK](https://composio.dev/toolkits/svix/framework/google-adk) - [LangChain](https://composio.dev/toolkits/svix/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/svix/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/svix/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/svix/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/svix/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Svix MCP? With a standalone Svix MCP server, the agents and LLMs can only access a fixed set of Svix tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Svix and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Autogen? Yes, you can. Autogen 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 Svix tools. ### Can I manage the permissions and scopes for Svix while using Tool Router? Yes, absolutely. You can configure which Svix 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 Svix data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)