Webhook Studio
OnlineKeyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.
What it can do: 17 tools
create_bucketProvision a new webhook endpoint (a "bucket") that captures incoming HTTP requests. Start here when building, testing or debugging a webhook handler. Works with NO account and no API key: in that case it returns endpointlist_bucketsList 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 idget_bucketFetch one webhook endpoint by id, including its url and inbox_url.delete_bucketPermanently delete a webhook endpoint and its captured events.latest_eventGet 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"list_eventsList 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 search over body, content type, method, typeget_eventFetch 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 targwait_for_eventBlock 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 returnsreplay_eventRe-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 thforward_bucketSet 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 destlist_deliveriesList 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".configure_verificationTurn 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 hlist_schemasList 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 kget_schemaFetch 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 dadiff_schemaCompare 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 readinggenerate_typesGenerate 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 marfind_correlation_keysList 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
Connect it
claude mcp add --transport http webhook-studio https://webhook-studio.com/mcpSettings → Connectors → Add custom connector
URL: https://webhook-studio.com/mcp{
"mcpServers": {
"webhook-studio": {
"url": "https://webhook-studio.com/mcp"
}
}
}{
"servers": {
"webhook-studio": {
"type": "http",
"url": "https://webhook-studio.com/mcp"
}
}
}Questions
What does Webhook Studio do?
Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic. It exposes 17 tools to AI assistants.
What tools does Webhook Studio provide?
17 tools, including create_bucket, list_buckets, get_bucket, delete_bucket, latest_event, list_events, get_event, wait_for_event, replay_event, forward_bucket, list_deliveries, configure_verification….
How do I connect Webhook Studio to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://webhook-studio.com/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does Webhook Studio require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is Webhook Studio online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes Webhook Studio?
webhook-studio.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.
Similar in Automation & Integrations
-
TypeformOnline · sign-in requiredOfficialPopular
Build and edit forms, manage automations and contacts, and analyze responses.
-
ZapierOnline · sign-in requiredOfficialPopular
Automate workflows across 10,000+ apps. Run one-off actions or build automations with triggers.
-
MakeOnline · sign-in requiredOfficialPopular
Build, run and debug Make automation scenarios.
-
IFTTT MCP serverOnline · sign-in requiredOfficial
Automate 1,000+ services from any MCP-compatible AI agent: build Applets, run actions and queries.
-
Ezoic Setup AssistantOnlineOfficial
Ezoic ads implementation assistant: integration docs, SDKs, and working, copyable setup code.
-
NicheDBOnlineOfficial
Sources in, feeds out: an open, ever-growing database of real-time public data, enriched.