SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Svix MCP with Mastra AI

Connect Mastra AI 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 Mastra AI 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 Mastra AI 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 SDKLlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Svix tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Svix tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Svix agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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

Prerequisites

Before starting, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Svix through MCP.
3

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_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 your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models
5

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session
6

Create a Tool Router session for Svix

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["svix"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Svix MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "svix" for Svix access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
7

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Svix toolkit
8

Create the Mastra agent

typescript
const agent = new Agent({
    name: "svix-mastra-agent",
    instructions: "You are an AI agent with Svix tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM
9

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

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

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        svix: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Svix toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

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

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["svix"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      svix: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "svix-mastra-agent",
    instructions: "You are an AI agent with Svix tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { svix: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Svix through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows
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

LlamaIndex logo

LlamaIndex

Use Svix MCP with LlamaIndex

CrewAI logo

CrewAI

Use Svix MCP with CrewAI

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. Mastra 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 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