The Svix Dashboard MCP server connects your coding agent to your Svix environment, so it can set up sources, read the webhooks you received, and debug failing deliveries without you leaving your editor.
Everything starts in the dashboard, which generates your token and the exact configuration for your agent.
Svix generates an access token for the current environment and opens the setup instructions.
Copy the ready-to-paste configuration for Claude Code, Cursor, VSCode, Codex, and more.
The server exposes your Svix Ingest setup as tools, so your agent can go from “set up Stripe webhooks” to a working, verified handler.
Create an Ingest source for a provider like Stripe or GitHub, and get back the URL to paste into that provider's webhook settings.
Add and update Ingest endpoints so incoming webhooks reach the handler you are writing, whether it's a tunnel URL or production.
List and read the webhooks a provider actually sent, so your agent writes the handler against the real payload instead of a guess.
Inspect delivery attempts with the exact status code and response body your handler returned, and the stats behind them.
Fetch or rotate endpoint signing secrets and custom headers, so signature verification works the first time.
Resend a single webhook to test a fix against a real, properly signed request, or replay everything an endpoint missed.
The dashboard fills these in with your generated token. Replace <your-token> with the token it gives you.
claude mcp add --transport http svix-dashboard "https://mcp.us.svix.com/dashboard" \
--header "Authorization: Bearer <your-token>"/mcp.For more details, see the Claude Code MCP documentation.
We are here for you.