Everything Svix builds to make AI agents good at webhooks: teaching them how to send and receive webhooks the way Svix's own engineers would, giving them tools to debug a broken delivery, and letting them receive webhooks without hosting a public HTTP server.
Three kinds of things live here:
| What it is | For | |
|---|---|---|
| Skills | Agent Skills: instructions that load into the agent's context on demand | Coding agents (Claude, Cursor, …) writing or reviewing a Svix integration |
| MCP servers | Tools an agent can call against a live Svix account | Debugging real webhook deliveries from your editor |
This repo is itself an Agent Plugins package, with dedicated manifests for other clients:
| Client | Manifest | Install |
|---|---|---|
| Claude Code | .claude-plugin/ |
/plugin marketplace add svix/ai then /plugin install svix@svix |
| Codex | .codex-plugin/plugin.json |
codex plugin marketplace add svix/ai then codex plugin add svix@svix, or /plugins in the Codex CLI |
| Any Agent Plugins client | plugin.json |
point the client at a clone of the repo |
Instructions an agent loads when it's about to touch Svix: planning an integration, wiring up the first webhook, reviewing an existing one, or writing a receiver. Two of them live in skills/, and that README has the full rundown.
Install them into any project:
npx skills add svix/aiFor more information, visit our docs
Agent runtimes usually receive webhooks by exposing an inbound HTTP route, which means a public URL, an open port, or a tunnel. These plugins invert that: they poll a Svix sink with the SDK's AutoConfigConsumer and hand each message to the runtime exactly as an inbound POST would. Nothing listens, so they work from a laptop behind NAT or a locked-down network, and the buffer in front means events survive a restart.
svix-openclaw: OpenClaw plugin. Polled payloads become TaskFlow actions, or get POSTed to the gateway's/hooks/wakeand/hooks/agentautomation hooks.svix-hermes: Hermes Agent gateway plugin. Each event flows through a route, prompt, and delivery pipeline, with responses going to a log, a GitHub comment, or any connected platform.
Each plugin's README covers install and configuration.
MIT