SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Svix MCP with CrewAI

Connect CrewAI to Svix MCP. List all webhook endpoints for app x, create a new webhook endpoint for payments, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Svix logoSvix
Api Key

Svix is an enterprise-grade webhooks service for sending webhooks reliably and securely. It helps developers deliver, track, and manage webhooks with advanced monitoring and retry logic.

37 Tools

Introduction

This guide walks you through connecting Svix to CrewAI using the Composio tool router. By the end, you'll have a working Svix agent that can send webhook messages, manage applications and endpoints, replay or recover failed webhooks, rotate endpoint secrets, and check delivery attempts through natural language commands.

This guide will help you understand how to give your CrewAI 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

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Svix connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Svix
  • Build a conversational loop where your agent can execute Svix operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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.

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

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Svix connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • 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

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Svix via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Svix MCP URL
6

Create a Composio Tool Router session for Svix

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["svix"])

url = session.mcp.url
What's happening:
  • You create a Svix only session through Composio
  • Composio returns an MCP HTTP URL that exposes Svix tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Svix and CrewAI:

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["svix"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Svix through Composio's Tool Router. The agent can perform Svix operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
TOOLS

Supported Tools

Every Svix action and event your agent gets out of the box.

Create Application

Tool to create a new Svix application.

Delete Svix Application

Permanently delete a Svix application by its ID or UID.

Get Application

Tool to retrieve details of a specific Svix application by its ID.

List Applications

Tool to list all applications.

Update Svix Application

Tool to update an existing Svix application by ID.

Get Attempt Details

Tool to retrieve details of a specific message attempt.

List Message Attempts

Tool to list all delivery attempts for a specific message.

Create Endpoint

Tool to create a new Svix webhook endpoint.

Delete Endpoint

Tool to delete an endpoint.

Get Endpoint

Tool to retrieve details of a specific endpoint.

List Endpoints

Tool to list all endpoints for a specific application.

Patch Endpoint

Tool to partially update an endpoint’s configuration.

Patch Endpoint Headers

Tool to partially update headers for a specific endpoint.

Recover Failed Webhooks

Tool to recover messages that failed to send to an endpoint.

Replay Missing Webhooks

Tool to replay missing webhooks for a specific endpoint.

Get Endpoint Secret

Tool to retrieve the secret for a specific endpoint.

Rotate Endpoint Secret

Tool to rotate the signing secret key for an endpoint.

Send Example Message

Tool to send a test message for a specific event type to an endpoint.

Get Endpoint Stats

Tool to retrieve basic statistics for a specific endpoint.

Get Endpoint Transformation

Tool to retrieve transformation settings for a specific endpoint.

Set Endpoint Transformation

Tool to set or update transformation settings for an endpoint.

Update Endpoint

Tool to update an existing endpoint or create it if it doesn't exist (upsert).

Update Endpoint Headers

Tool to completely replace headers for a specific endpoint.

Create Event Type

Create a new event type in Svix or unarchive an existing one.

Delete Event Type

Tool to delete an event type.

Get Event Type

Retrieve details of a specific event type by its name.

List Event Types

Tool to retrieve a list of all event types.

Update Event Type

Update an existing event type's description, schema, feature flags, or archive status.

Create Integration

Tool to create a new integration for a specific application.

Delete Integration

Permanently delete an integration from a Svix application.

Get Integration

Tool to retrieve details of a specific integration.

List Integrations

Tool to list all integrations for a specific application.

Update Integration

Update an existing integration by application and integration ID, setting its name and optionally its feature flags.

Create Message

Tool to create a new message for a specific application in Svix.

Get Message

Retrieve details of a specific Svix message by application and message ID, including its metadata and payload.

List Messages

Tool to list all messages for a specific application.

Create Source

Creates a new Svix Ingest source for receiving webhooks from external providers.

FRAMEWORKS

How to build Svix MCP Agent with another framework

Claude Code logo

Claude Code

Use Svix MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Svix MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Svix MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Svix MCP with Claude Agent SDK

Codex logo

Codex

Use Svix MCP with Codex

OpenClaw logo

OpenClaw

Use Svix MCP with OpenClaw

Hermes logo

Hermes

Use Svix MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Svix MCP with Atomic Agent

Google ADK logo

Google ADK

Use Svix MCP with Google ADK

LangChain logo

LangChain

Use Svix MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Svix MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Svix MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Svix MCP with LlamaIndex

Pydantic AI logo

Pydantic AI

Use Svix MCP with Pydantic AI

AutoGen logo

AutoGen

Use Svix MCP with AutoGen

FAQ

Frequently asked questions

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.

Yes, you can. CrewAI 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.

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.

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.

Start with Svix.It takes 30 seconds.

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

Start building