Webhook URLs for AI agents: receive, wait for, replay, sign and verify webhooks (Stripe, GitHub…).
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Receive, forward, sign and verify webhooks from your terminal, your test suite and your AI agent.
One package: a CLI (webhook-toolkit, alias whtk), a typed library and an MCP server, backed by webhook-toolkit.com.
That's it: no account, no config. You get a public URL; paste it into Stripe, GitHub, Shopify or any other sender, and every webhook shows up in your terminal and is re-sent to your local handler:
Every request is also kept in a web inspector (headers, raw body, replay), so nothing is lost when your handler crashes.
| Command | What it does |
|---|---|
whtk listen [--forward <url>] | Public URL + live stream of incoming requests, optionally re-sent to localhost. Reuses your last URL while it is alive (--new for a fresh one). |
whtk relay --to <url|port> | Real tunnel: callers get your local app's response. Paid. |
whtk sign <provider> --secret <s> | Build a validly signed webhook: prints headers + a ready-to-run curl, or sends it with --send. |
whtk verify <provider> --secret <s> … | Check a signature, and when it fails, say why. |
whtk replay <token> <id> --to <url> | Re-send a captured request from your machine (localhost works). |
whtk requests <token> | List captured requests (--json for scripts). |
whtk endpoints | List your account's URLs. |
whtk login / logout / whoami | Save, remove or inspect your API key. |
whtk mcp | Start the MCP server on stdio. |
A few things worth knowing:
…/r/<token>/stripe?x=1 is forwarded to http://localhost:3000/webhooks/stripe?x=1, so one URL can feed several handlers.host and content-length), so signature checks in your handler pass exactly as in production.--json prints NDJSON (listening, request, forward events) for scripting: whtk listen -f 3000 --json | jq .request.event.NO_COLOR, FORCE_COLOR and are off when output is not a terminal.The verifier replays the usual mistakes (whitespace in the secret, added or stripped trailing newline, CRLF conversion, expired timestamp, and for Twilio: http vs https, port, query string, trailing slash, repeated parameters) and tells you which one matches. The same logic powers the online signature validator.
The library gives your tests a real public URL and a way to wait for what lands on it. It works anonymously; set WEBHOOK_TOOLKIT_KEY in CI for permanent URLs and higher limits.
waitForRequest checks requests that already arrived since the endpoint was created, then long-polls until timeoutMs, so the order of "trigger" and "wait" does not matter. It rejects with a WebhookToolkitError (code: "timeout") when nothing matched.
To test your handler without any network at all, sign the payload locally:
The package is ESM-only. CommonJS test runners work on Node ≥ 20.19 / 22.12 (native
require(esm)); Jest needs its ESM mode.
webhook-toolkit mcp is a Model Context Protocol server. Your coding agent can create a webhook URL, wait for the delivery after triggering it, read the payload, then replay it or send freshly signed events to your localhost handler while it fixes the code.
The API key is optional: everything except list_webhook_urls and explain_webhook_request works anonymously.
Claude Code
Cursor (.cursor/mcp.json), Windsurf (~/.codeium/windsurf/mcp_config.json), Claude Desktop (claude_desktop_config.json)
VS Code (.vscode/mcp.json)
Codex CLI (~/.codex/config.toml)
ChatGPT, Claude.ai and other remote-capable clients: add a custom connector pointing at the hosted server, nothing to install:
(Streamable HTTP, optional Authorization: Bearer whk_….) The hosted server cannot reach your machine, so replaying to localhost and send_signed_webhook need the local server above.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/webhook-toolkit)<a href="https://allmcps.com/mcp/webhook-toolkit"><img src="https://allmcps.com/api/badge/webhook-toolkit?style=directory" alt="Webhook Toolkit on AllMCPs" /></a>