Svix is a webhook delivery platform. Use it to create applications, send webhook messages, manage endpoints, track delivery attempts, retry failed deliveries, and manage event types. This bundle uses the Svix Environment API key.
This MCP Bundle Server is compatible with any MCP client including Claude Desktop, Cursor, and other Model Context Protocol implementations.
Create a new Svix application (represents one of your customers/webhook consumers). Provide a name and optionally a UID, rate limit, and metadata.
Create a new webhook endpoint (receiver URL) for an application. Optionally filter by event types or channels.
Create a new event type to categorize webhook messages. Provide a name (e.g. 'order.completed') and description.
Send a webhook message to all endpoints subscribed to the given event type in an application. This is the core 'send webhook' operation.
Delete a Svix application and all its endpoints, messages, and delivery history. This is irreversible.
Delete an event type. Endpoints already filtering for this type will continue to work. This is irreversible.
Get details of a specific Svix application by ID or UID. Returns name, UID, metadata, rate limit, created/updated timestamps.
Generate a one-time-use URL for the Svix App Portal. The portal lets your customers manage their own endpoints and view delivery logs.
Get full details of a specific delivery attempt including URL, response status code, response body, duration, and trigger type.
Get details of a specific endpoint including its URL, filter types, channels, rate limit, and status.
Get the signing secret for an endpoint. Used by webhook consumers to verify message signatures.
Get delivery statistics for an endpoint: success count, failure count, and sending status.
Get environment settings including retry policy, HTTPS enforcement, channels, transformations, branding/white-label config, and feature flags.
Get a specific event type by name. Returns description, schemas, archived status, and timestamps.
Get a specific message by ID. Returns event type, payload, channels, tags, and timestamps.
List all applications (customer webhook targets) in your Svix environment. Returns app IDs, names, UIDs, metadata, and rate limits with pagination.
List messages that have been attempted on a specific endpoint. Shows which messages were delivered, failed, or are pending.
List delivery attempts for a specific endpoint. Use to check which messages were delivered, failed, or are pending for this endpoint.
List delivery attempts for a specific message. Shows which endpoints received the message, their HTTP status codes, and timestamps.
List all endpoints (webhook receiver URLs) for a specific Svix application. Returns endpoint URLs, IDs, filter types, channels, rate limits.
List all defined event types in your Svix environment. Event types categorize webhook messages (e.g. 'invoice.paid', 'user.created').
List ingest sources — external services that push events into Svix for processing and forwarding to your application endpoints.
List integrations for an application. Integrations are pre-built connectors (e.g. Slack, Discord) that simplify webhook delivery.
List messages (webhook events) sent to an application. Filter by event type or channel. Returns message IDs, event types, payloads, and timestamps.
List operational webhook endpoints. These receive Svix system events (e.g. message.attempt.exhausted) about your own webhook infrastructure.
Resend all failed messages to an endpoint since a given time. Use this to recover from endpoint outages.
Resend a specific message to a specific endpoint. Use when a delivery attempt failed and you want to manually retry.
Rotate the signing secret for an endpoint. The old secret remains valid for 24 hours for a graceful transition.
Update an existing application's name, UID, rate limit, or metadata. Only provided fields are changed.
Update an existing endpoint's URL, filters, rate limit, or disabled state. Only provided fields are changed.
Connect this Svix MCP Bundle Server to any MCP client in minutes
Compatible with Claude Desktop, Cursor, and all Model Context Protocol clients
Model Context Protocol lets AI tools call external capabilities securely through a single URL. This bundle groups tools behind an MCP endpoint that many clients can use.
Skip the manual setup! Use the .mcpb file format for one-click installation. Check the Claude Desktop tab for setup instructions.
Select ChatGPT, Cursor, Claude Code, or another tab for copy-paste config.