Webhook Studio
Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: automate business workflows.Similar tools
Listed for the same task: automate business workflowsReviews
No review yet. Used Webhook Studio? Be the first to help others choose.What it does
Webhook Studio is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: api integration. That makes it a candidate for tasks such as automate business workflows or build an internal tool.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)Hosted endpoint
https://webhook-studio.com/mcpstreamable-http
In Claude Code: claude mcp add --transport http webhook-studio https://webhook-studio.com/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"webhook-studio": {
"url": "https://webhook-studio.com/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 2d agoONLINE Webhook Studio answered an MCP connection on 13 Nov 2026 and introduced itself as webhook-studio 0.1.1 (MCP protocol 2025-06-18).
17 tools offered to AI assistants
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 stalist_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.get_bucket· Fetch one webhook endpoint by id, including its url and inbox_url.delete_bucket· Permanently delete a webhook endpoint and its captured events.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 matlist_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 search over body, content type, method, type and labels; space-sget_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 bacwait_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 arrireplay_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 verifiesforward_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 routinglist_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".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
Show 5 more
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 afteget_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.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. frgenerate_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, insteafind_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 Strip
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://webhook-studio.com/mcp | DECLARED | SRC-001 Official MCP Registry | 6h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 6h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 6h ago |
| Website | https://webhook-studio.com/mcp/setup | DECLARED | SRC-001 Official MCP Registry | 6h ago |
| Repository | https://github.com/lestertww/webhookstudio | DECLARED | SRC-001 Official MCP Registry | 6h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 6h ago |
| Version | 0.1.1 | DECLARED | SRC-001 Official MCP Registry | 6h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 6h ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Webhook Studio still online?
Free alerts · no account▲ 0Do you run Webhook Studio? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Webhook Studio
How do I connect Webhook Studio?
Use the hosted endpoint https://webhook-studio.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Webhook Studio offer?
When Electra Index connected on 13 Nov 2026, it listed 17 tools: create_bucket, list_buckets, get_bucket, delete_bucket, latest_event, list_events, get_event, wait_for_event and more. The full list is in "Live check" above.
Is Webhook Studio online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.
What can I use Webhook Studio for?
Based on its description, it is most relevant to: automate business workflows, build an internal tool, integrate two APIs, build data pipelines.