Webhook Studio is answering right now. Last checked 8 min ago. It exposes 17 tools. Last commit 21 Aug 2026.
Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.
Uptime history
47 days of history
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
17
Tools
read from the server
298 ms
Response time
average over 24h
0
Stars
last commit 21 Aug 2026
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 August 2026. No other catalogue keeps this.
21 Aug
a tool changed version
Nothing serious here today
Today is the operative word: we check Webhook Studio every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.
run in your terminal
claude mcp add webhooks --transport http https://webhook-studio.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"webhooks": {
"url": "https://webhook-studio.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.webhooks]
url = "https://webhook-studio.com/mcp".cursor/mcp.json
{
"mcpServers": {
"webhooks": {
"url": "https://webhook-studio.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"webhooks": {
"url": "https://webhook-studio.com/mcp"
}
}
}Available tools 17
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
bucket
create_bucket
Provision a new webhook endpoint (a "bucket") that captures incoming HTTP requests. Returns its id, public ingest url to point a provider at, inbox_url (the live human view to hand back), and signing secret. Pass external_ref — your own stable name like "acme-api:stripe" — so you can re-find this exact bucket later with list_buckets after losing context.
delete_bucket
Permanently delete a webhook endpoint and its captured events.
get_bucket
Fetch one webhook endpoint by id, including its url and inbox_url.
buckets
list_buckets
List your webhook endpoints. Pass external_ref to fetch the specific bucket you created earlier under that name — this is how you re-anchor after losing the conversation, since you never need to have stored the bucket id.
configure
configure_verification
Turn on HMAC signature verification for a bucket using the provider's own signing secret (e.g. Stripe's whsec_). This is how you finish a "verified webhook" integration end to end. Set secret to the provider secret and hmac_enabled:true in the same call; the signature scheme is auto-detected from the header shape.
correlation
find_correlation_keys
List the correlation-key candidates for a learned schema — the fields that look like identifiers (e.g. data.object.id), ranked by how consistently they appear. These are the fields to group events by when reconstructing a lifecycle (a Stripe payment_intent across created -> succeeded, a GitHub PR across its events). Derived from real traffic, so it reflects what THIS account actually receives.
deliveries
list_deliveries
List outbound delivery attempts for a bucket, newest first, with the full request and response of each. Pass success:false to see only failures — the direct answer to "which of my forwards are broken and why".
diff
diff_schema
Compare two versions of a learned schema and get exactly which fields were added, removed or changed type, each flagged as breaking or not. This is the "why did my handler start failing" answer, produced without reading a single payload. from defaults to the version before to.
event
get_event
Fetch one captured event by id with its full headers, body, signature verification result (and failure reason), and every outbound delivery attempt. This is how you find out whether your forward actually reached its target and what came back.
events
list_events
List events captured by a bucket, newest first, with composable filters: since/until (ISO 8601 or YYYY-MM-DD), provider, type, method, signature_valid, and q (case-insensitive substring over body, content type, method, type and labels). Use cursor for the next page.
forward
forward_bucket
Set up standing forwarding from a bucket to a URL. Pass forward_all:true to forward every event, or condition_tree to forward only matching events (same AND/OR condition grammar the routing engine uses). Creates the destination and routing rule in one call.
generate
generate_types
Generate types, a runtime validator, or a full handler from a learned schema — the payoff of the knowledge layer. Everything is derived from the payloads this account ACTUALLY received, with genuinely-optional fields marked optional, instead of a plausible-but-wrong guess from a model's memory of the provider docs. Pass lang for a bare type (typescript / json-schema / zod), or framework (next / express) for a ready-to-paste handler that validates and hands back a fully-typed event.
latest
latest_event
Get the single most recent event captured by a bucket, optionally filtered by provider and event type. Returns one event with its headers, body and delivery results — the one-shot answer to "what did Stripe last send me". 404 if nothing matches, so you never index into an empty list.
replay
replay_event
Re-send a captured event to any URL — the test runner for a handler you just wrote. preserve_headers defaults to true so the original signature header (e.g. Stripe-Signature) arrives intact. If you changed the body or the receiver verifies with a different secret, pass resign_with (the dev's own signing secret) so the payload is re-signed and their verification code passes unmodified. Returns the response status, latency and body.
schema
get_schema
Fetch one learned schema with every field, its type, whether it is optional, and how often it actually appears — the real shape of the payload, derived from what this account received rather than guessed from training data.
schemas
list_schemas
List the payload schemas Webhook Studio has learned from this account's real traffic, optionally filtered by provider and event_type. These outlive the payloads they were learned from, so this answers "what shapes do I know about" even after old events are gone. Start here to discover what you can generate types or diffs for.
wait
wait_for_event
Block until the next matching event arrives on a bucket, or until the timeout. Use this to turn "go click Send test webhook in Stripe" into a synchronous step: call it, tell the human to trigger the event, and it returns as soon as one arrives. Filters (provider, type) mean unrelated traffic does not wake it. Returns the event, or nothing if it times out.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://webhook-studio.com/mcp | streamable-http | answering | 289 ms | 8 min ago |
Alternatives to Webhook Studio
same job, measured the same wayOtterkit
by useotterkit
Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.
Keploy
by keploy
End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
Hookden
by pages-hookden
Webhook capture bins for agents: get a URL, wait for webhooks, set replies, verify signatures.
Webhook AI MCP
by csoai-org
Webhook Ai tools for AI agents. Capabilities: validate webhook signature, log webhook event, replay
Ryudi84
by ryudi84
MCP server for generating REST API boilerplate and Express endpoints.
AnyHook (moved)
by gba3124
Moved to net.anyhook/anyhook. Webhook relay for agents: keyless quickstart, replay, mock.
I
MCP API Doc Generator
by vpatser1
Generate OpenAPI 3.1 specs, endpoint docs, TypeScript SDKs, and test suites from code
Hookline
by hookline
Hookline MCP — create webhook endpoints, inspect requests, and validate payloads from AI agents.
Webhook Studio — questions
Answers built from our own checks of this server.
What can Webhook Studio do?
It exposes 17 tools, read directly from the server on our last check. Among them: configure_verification, create_bucket, delete_bucket, diff_schema, find_correlation_keys, forward_bucket and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Webhook Studio working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 298 ms. The bar chart above shows every period we have measured.
How do I connect Webhook Studio?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Webhook Studio need an API key?
No. Webhook Studio completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Webhook Studio?
It answers our handshake in 298 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Webhook Studio open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.