How to integrate Svix MCP with Google ADK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Svix Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting Svix to Google ADK 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, get delivery attempts for message id 12345 through natural language commands.

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

TL;DR

Here's what you'll learn:
  • Get a Svix account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Svix
  • Build an agent that connects to Svix through MCP
  • Interact with Svix using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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 & Triggers

Tools
Create ApplicationTool to create a new svix application.
Delete Svix ApplicationTool to delete an application by its id.
Get ApplicationTool to retrieve details of a specific svix application by its id.
List ApplicationsTool to list all applications.
Update Svix ApplicationTool to update an existing svix application by id.
Get Attempt DetailsTool to retrieve details of a specific message attempt.
List Message AttemptsTool to list all delivery attempts for a specific message.
Create EndpointTool to create a new svix webhook endpoint.
Delete EndpointTool to delete an endpoint.
Get EndpointTool to retrieve details of a specific endpoint.
List EndpointsTool to list all endpoints for a specific application.
Patch EndpointTool to partially update an endpoint’s configuration.
Patch Endpoint HeadersTool to partially update headers for a specific endpoint.
Recover Failed WebhooksTool to recover messages that failed to send to an endpoint.
Replay Missing WebhooksTool to replay missing webhooks for a specific endpoint.
Get Endpoint SecretTool to retrieve the secret for a specific endpoint.
Rotate Endpoint SecretTool to rotate the signing secret key for an endpoint.
Send Example MessageTool to send a test message for a specific event type to an endpoint.
Get Endpoint StatsTool to retrieve basic statistics for a specific endpoint.
Get Endpoint TransformationTool to retrieve transformation settings for a specific endpoint.
Set Endpoint TransformationTool to set or update transformation settings for an endpoint.
Update EndpointTool to update an existing endpoint.
Update Endpoint HeadersTool to completely replace headers for a specific endpoint.
Create Event TypeTool to create a new event type or unarchive an existing one.
Delete Event TypeTool to delete an event type.
Get Event TypeTool to retrieve details of a specific event type by its id.
List Event TypesTool to retrieve a list of all event types.
Update Event TypeTool to update an existing event type by id.
Create IntegrationTool to create a new integration for a specific application.
Delete IntegrationTool to delete an integration.
Get IntegrationTool to retrieve details of a specific integration.
List IntegrationsTool to list all integrations for a specific application.
Update IntegrationTool to update an existing integration by id.
Create MessageTool to create a new message for a specific application in svix.
Get MessageTool to retrieve details of a specific message by its id.
List MessagesTool to list all messages for a specific application.
Create SourceTool to create a source for message ingestion.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio-google python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Svix via MCP
  • composio-google provides the Google ADK provider
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
print("Initializing Composio client...")
composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

print("Creating Composio session...")
composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["svix"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url
print(f"Composio MCP HTTP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
print("Creating Composio toolset for the agent...")
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )
)

root_agent = Agent(
    model="gemini-2.5-pro",
    name="composio_agent",
    description="An agent that uses Svix tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Svix operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web
Execute the agent from the project root. The web command opens a web portal where you can chat with the agent. What's happening:
  • adk run runs the agent in CLI mode
  • adk web opens a web UI for interactive testing

Complete Code

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

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

def main():
    try:
        load_dotenv()

        warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

        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.")

        print("Initializing Composio client...")
        composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

        print("Creating Composio session...")
        composio_session = composio_client.create(
            user_id=COMPOSIO_USER_ID,
            toolkits=["svix"],
        )

        COMPOSIO_MCP_URL = composio_session.mcp.url
        print(f"Composio MCP HTTP URL: {COMPOSIO_MCP_URL}")

        print("Creating Composio toolset for the agent...")
        composio_toolset = McpToolset(
            connection_params=StreamableHTTPConnectionParams(
                url=COMPOSIO_MCP_URL,
                headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
            )
        )

        root_agent = Agent(
            model="gemini-2.5-pro",
            name="composio_agent",
            description="An agent that uses Svix tools to perform actions.",
            instruction=(
                "You are a helpful assistant connected to Composio. "
                "You have the following tools available: "
                "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
                "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
                "Use these tools to help users with Svix operations."
            ),
            tools=[composio_toolset],
        )

        print("\nAgent setup complete. You can now run this agent directly ;)")

    except Exception as e:
        print(f"\nAn error occurred during agent setup: {e}")

if __name__ == "__main__":
    main()

Conclusion

You've successfully integrated Svix with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Svix using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Svix tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

How to build Svix MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Svix MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Svix MCP with Claude Agent SDK

LangChain

LangChain

Use Svix MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Svix MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Svix MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Svix MCP with LlamaIndex

CrewAI

CrewAI

Use Svix MCP with CrewAI

FAQ

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 Google ADK?

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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.

Book a call↗Get started for free