# Svix MCP

> Svix lets you manage your entire webhook infrastructure using natural conversation with your AI client. You'll take full control of complex event-driven workflows, configuring applications and endpoints without touching a dashboard. Need to check why an invoice notification failed? Your agent handles the debugging by listing message attempts or retrieving delivery status for specific payloads. It’s like having a dedicated DevOps engineer running live right inside your chat window.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Tags:** webhooks, api-infrastructure, event-delivery, message-queues, endpoint-management, real-time-sync

## Description

Managing webhooks usually means jumping between dashboards, digging through obscure logs, and manually updating configuration files just to test one single endpoint. This MCP changes that. You connect Svix and give your AI client the power to handle all of your event delivery needs conversationally. Instead of guessing whether a message got delivered or why an application failed to send data, you simply ask your agent to check it. It lets you group related services by listing applications, set up new receiving URLs via endpoint configuration, and even manually trigger test messages for verification. Because Vinkius hosts this MCP, you get direct, natural language access to all these core event management functions—from creating a whole application down to deleting old endpoints. Your AI client becomes the central hub that keeps your entire webhook lifecycle running smoothly.

## Tools

### create_application
Builds a new, logical grouping for your webhooks.

### create_endpoint
Sets up a new destination URL that will receive webhook events.

### create_message
Sends an immediate test message to simulate a real event payload.

### delete_application
Removes an entire set of webhooks and associated endpoints.

### delete_endpoint
Takes down a specific receiving URL when it's no longer needed.

### get_application
Retrieves all the details for one specific webhook application by its ID.

### get_endpoint
Shows the full configuration and status of a single endpoint URL.

### get_message
Fetches specific details about one test message, including its event type.

### list_applications
Shows an overview of every webhook application you have set up.

### list_endpoint_attempts
Retrieves a list of past delivery attempts and their status for a given endpoint.

### list_endpoints
Lists all the active endpoints associated with a specific application.

### list_message_attempts
Shows records of past message deliveries and their corresponding attempt statuses.

### list_messages
Provides an overview list of all messages that were sent under a specific application.

### update_application
Modifies the settings or name of an existing webhook application.

### update_endpoint
Changes the URL, filters, or status of an already configured endpoint.

## Prompt Examples

**Prompt:** 
```
List all my Svix applications.
```

**Response:** 
```
I've retrieved your applications. You have 2 active apps: 'Main API' (ID: app_2X...) and 'Billing Service' (ID: app_9Y...). Which one would you like to inspect?
```

**Prompt:** 
```
Create a new endpoint for app_2X... with URL https://webhook.site/test and subscribe to 'user.created' events.
```

**Response:** 
```
Endpoint created successfully! The new endpoint ID is ep_3Z... and it is now configured to receive 'user.created' events at the specified URL.
```

**Prompt:** 
```
Show me the details for message msg_4W...
```

**Response:** 
```
Fetching message details... Message msg_4W... was sent with event type 'invoice.paid'. It has been successfully delivered to 1 endpoint and is currently pending on another.
```

## Capabilities

### Configure Webhook Applications
Group and organize related services by listing, creating, or updating specific applications.

### Manage Destination Endpoints
Create new receiving URLs, modify existing endpoints, or delete stale ones for a given application.

### Monitor Message Payloads and Delivery Status
Send test messages to verify routes, list message attempts, and retrieve detailed status for any event payload.

### Diagnose Failures and History
List all endpoint delivery attempts or review historical message failures to pinpoint exactly where an integration broke.

## Use Cases

### Validating Customer Payment Flows
A product integration lead needs to confirm that a payment webhook hit the correct destination. Instead of logging in to the portal, they ask their agent to get message details for the specific transaction ID, verifying both delivery status and the payload content.

### Troubleshooting Failed API Calls
A backend engineer sees a failure notification. They use list endpoint attempts on their agent, telling it which application failed, immediately identifying the broken URL and its last known error code.

### Onboarding New Microservices
A DevOps team needs to connect three new services. They ask their agent to create three separate applications and configure corresponding endpoints for each service in a single, structured conversation.

### Auditing Webhook Activity
An operations manager needs an audit trail of all messages sent last week. They use list messages and then follow up by listing message attempts to ensure every record was successfully processed.

## Benefits

- You skip the dashboard. Instead of manually checking logs, you ask your agent to list endpoint attempts or get message details immediately.
- Debugging is faster because you don't have to copy/paste IDs. You just tell your agent to check a specific application and it pulls up all its associated endpoints.
- Setup and teardown are instant. Need to delete old webhook destinations? Use the delete endpoint tool instead of navigating deep into settings menus.
- Testing is built-in. Instead of writing a script, you simply ask your agent to create a message and check delivery status for immediate verification.
- Complete lifecycle control is available. You can use list applications to see everything currently running, or update application details without leaving your chat window.

## How It Works

The bottom line is that your AI client treats webhook management as a natural conversation rather than a series of clicks and forms.

1. First, subscribe to this MCP and provide your Svix API Secret Key within your AI client.
2. Next, tell your agent what you need: 'List all my applications,' or 'Create a new endpoint for X.'
3. The agent executes the command against the service, retrieving real-time data like delivery status, application details, or lists of failed attempts.

## Frequently Asked Questions

**How do I list all my webhooks applications using Svix MCP?**
You use the list_applications tool. This instantly pulls up an overview of every webhook application you have set up in your account.

**Can I test a message delivery with the Svix MCP?**
Yes, you can trigger a test event using create_message. After sending it, use list message attempts to confirm where it delivered successfully.

**Which tool do I use if an endpoint URL is broken?**
You should start by listing endpoint attempts for that specific application. This helps pinpoint the exact failure and whether the issue is with the payload or the destination itself.

**Does Svix MCP let me update endpoints in natural language?**
Absolutely. You use the update_endpoint tool to change a URL, modify its filters, or change its status without having to manually edit the configuration dashboard.

**I need to clean up old webhooks; what should I do?**
Use delete application to remove entire groups of endpoints, or use delete_endpoint if you only want to retire a single, specific receiving URL.