API Tools
webhook-studio.com
Manages webhook endpoints for capturing and inspecting HTTP requests.
ENDPOINT 1
https://webhook-studio.com/mcp
MCP server metadata
- Name
- webhook-studio
- Version
- 0.1.0
Webhook Studio: capture, forward, replay and learn the shape of webhooks. Provision with create_bucket (pass external_ref to re-find it later), point a provider at the returned url, then wait_for_event / latest_event to see traffic. Prove a handler with replay_event (preserve_headers or resign_with), confirm forwards with list_deliveries, and turn real payloads into types with generate_types. Hand the human the inbox_url when done.
Known tools 17
create_bucketProvision a new webhook endpoint (a "bucket") that captures incoming HTTP requests.
list_bucketsList your webhook endpoints.
get_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.
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 substring over body, content type, method, type and labels).
get_eventFetch one captured event by id with its full headers, body, signature verification result (and failure reason), and every outbound delivery attempt.
wait_for_eventBlock until the next matching event arrives on a bucket, or until the timeout.
replay_eventRe-send a captured event to any URL — the test runner for a handler you just wrote.
forward_bucketSet up standing forwarding from a bucket to a URL.
list_deliveriesList outbound delivery attempts for a bucket, newest first, with the full request and response of each.
configure_verificationTurn on HMAC signature verification for a bucket using the provider's own signing secret (e.g.
list_schemasList the payload schemas Webhook Studio has learned from this account's real traffic, optionally filtered by provider and event_type.
get_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 data.
diff_schemaCompare two versions of a learned schema and get exactly which fields were added, removed or changed type, each flagged as breaking or not.
generate_typesGenerate types, a runtime validator, or a full handler from a learned schema — the payoff of the knowledge layer.
find_correlation_keysList the correlation-key candidates for a learned schema — the fields that look like identifiers (e.g.