Send and debug webhooks — applications, endpoints, messages, delivery attempts and replays. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"svix": {
"url": "https://svix.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"svix": {
"type": "http",
"url": "https://svix.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Svix API key.
Create one in the Svix dashboard → API Access. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Svix API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Svix connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
svix_list_applications | read | List applications List the applications (your tenants/customers) in the Svix environment. Svix REST: GET /api/v1/app. |
svix_get_application | read | Get one application Fetch a single application by its Svix id or your own uid. Svix REST: GET /api/v1/app/{app_id}. |
svix_list_endpoints | read | List endpoints List the webhook endpoints registered for one application. Svix REST: GET /api/v1/app/{app_id}/endpoint. |
svix_get_endpoint | read | Get one endpoint Fetch a single webhook endpoint, including its URL, subscribed event types and channels. Svix REST: GET /api/v1/app/{app_id}/endpoint/{endpoint_id}. |
svix_get_endpoint_stats | read | Get endpoint delivery stats Read delivery statistics for one endpoint — counts of success, pending, sending and fail. The fastest way to see whether an endpoint is healthy. Svix REST: GET /api/v1/app/{app_id}/endpoint/{endpoint_id}/stats. |
svix_list_messages | read | List messages List the webhook messages sent for one application, newest first. Filter by event type, channel, tag or time window. Svix REST: GET /api/v1/app/{app_id}/msg. |
svix_get_message | read | Get one message Fetch a single message, including its event type and payload. Svix REST: GET /api/v1/app/{app_id}/msg/{msg_id}. |
svix_list_attempts_by_message | read | List delivery attempts for a message List every delivery attempt Svix made for one message, across endpoints — status, response code and body. This is the tool for answering 'why did this webhook not arrive?'. Svix REST: GET /api/v1/app/{app_id}/attempt/msg/{msg_id}. |
svix_list_attempts_by_endpoint | read | List delivery attempts for an endpoint List delivery attempts against one endpoint, newest first. Filter by status to find the failures. Svix REST: GET /api/v1/app/{app_id}/attempt/endpoint/{endpoint_id}. |
svix_list_endpoint_messages | read | List messages for an endpoint List the messages destined for one endpoint, with each message's delivery status. Svix REST: GET /api/v1/app/{app_id}/endpoint/{endpoint_id}/msg. |
svix_list_event_types | read | List event types List the event types defined in the environment — the catalogue endpoints can subscribe to. Svix REST: GET /api/v1/event-type. |
svix_get_event_type | read | Get one event type Fetch a single event type by name, including its description and JSON schema. Svix REST: GET /api/v1/event-type/{event_type_name}. |
svix_list_background_tasks | read | List background tasks List Svix background tasks (bulk replays, expunges, imports) with their status. Use it to follow up a recover or replay. Svix REST: GET /api/v1/background-task. |
svix_health | read | Check API health Check that the Svix API is reachable and the API key works. Returns 200 with an empty body when healthy. Svix REST: GET /api/v1/health. |
svix_create_application | write | Create an application Create a new application (one tenant/customer of yours) in the Svix environment. Svix REST: POST /api/v1/app. |
svix_create_endpoint | write | Create an endpoint Register a webhook endpoint URL for one application, optionally scoped to specific event types and channels. Svix REST: POST /api/v1/app/{app_id}/endpoint. |
svix_send_message | write | Send a message Send a webhook message to every endpoint of an application subscribed to the event type. This delivers real traffic to your customers' URLs. Svix REST: POST /api/v1/app/{app_id}/msg. |
svix_resend_message | write | Resend a message to one endpoint Queue one message for redelivery to one endpoint. The usual fix after a customer's endpoint was down. Svix REST: POST /api/v1/app/{app_id}/msg/{msg_id}/endpoint/{endpoint_id}/resend. |
svix_recover_endpoint | write | Recover an endpoint's failed messages Replay every failed message for one endpoint since a timestamp. Runs as a background task — follow it with svix_list_background_tasks. Svix REST: POST /api/v1/app/{app_id}/endpoint/{endpoint_id}/recover. |
svix_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
svix_request_feature | Request a missing feature Tell usefulapi that the user needs something the Svix tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
svix_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Svix tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
svix_cancel_subscription | Cancel the Pro subscription Cancel the caller's Svix Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run svix_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Svix server only. Subscribe with svix_upgrade (it returns a Stripe Checkout link). Cancel any time with svix_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running svix_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Svix. The server calls the Svix API with your own Svix access, so it sees only the data that your account can see.
The login page asks for your Svix API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Svix API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Svix API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Svix.
Yes, if you approve it. 5 of the 19 Svix tools can create or change data. The other 14 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Svix server only. Run svix_usage_status to see how many calls you used.
Ask the AI to run svix_upgrade: it returns a Stripe Checkout link. To cancel, run svix_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with svix_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.