Serveur MCP
Webhook Studio
com.webhook-studio/webhooks
Ce que fait ce MCP
Creates webhook endpoints, captures and replays events, forwards traffic, verifies signatures, learns payload schemas, and generates types or handlers.
Capacités
Outils
17
outils
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.
Schéma d’entrée
{'type': 'object', 'required': ['bucket_id'], 'properties': {'secret': {'type': 'string', 'description': "The provider's signing secret (≥16 chars)."}, 'bucket_id': {'type': 'string', 'description': 'The endpoint id.'}, 'on_failure': {'enum': ['reject', 'accept_log'], 'type': 'string', 'description': 'What to do with a failed signature.'}, 'header_name': {'type': 'string', 'description': 'Signature header to read (auto-detected if omitted).'}, 'hmac_enabled': {'type': 'boolean', 'description': 'Enable verification.'}, 'tolerance_seconds': {'type': 'number', 'description': 'Max timestamp skew allowed, in seconds.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': [], 'properties': {'name': {'type': 'string', 'description': 'Human label for the bucket.'}, 'environment': {'enum': ['production', 'staging', 'sandbox', 'development'], 'type': 'string', 'description': 'Deployment environment.'}, 'external_ref': {'type': 'string', 'description': 'Your own stable identifier (unique per account) for idempotent re-provisioning and re-finding.'}}, 'additionalProperties': False}
delete_bucket
Permanently delete a webhook endpoint and its captured events.
Schéma d’entrée
{'type': 'object', 'required': ['bucket_id'], 'properties': {'bucket_id': {'type': 'string', 'description': 'The endpoint id.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': ['schema_id'], 'properties': {'to': {'type': 'string', 'description': 'Target version number, or "current".'}, 'from': {'type': 'string', 'description': 'Baseline version number (defaults to the one before "to").'}, 'schema_id': {'type': 'string', 'description': 'The schema id.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': ['schema_id'], 'properties': {'version': {'type': 'string', 'description': 'Version number, or "current" (the default).'}, 'schema_id': {'type': 'string', 'description': 'The schema id.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': ['bucket_id', 'url'], 'properties': {'url': {'type': 'string', 'description': 'Destination URL to forward to.'}, 'name': {'type': 'string', 'description': 'Optional label for the destination.'}, 'bucket_id': {'type': 'string', 'description': 'The endpoint id.'}, 'rule_name': {'type': 'string', 'description': 'Optional name for the routing rule when using condition_tree.'}, 'forward_all': {'type': 'boolean', 'description': 'Forward every event unconditionally.'}, 'condition_tree': {'type': 'object', 'description': 'A condition tree (AND/OR of field comparisons) to forward only matching events. Mutually exclusive with forward_all.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': ['schema_id'], 'properties': {'lang': {'enum': ['typescript', 'json-schema', 'zod'], 'type': 'string', 'description': 'Output format for a bare type.'}, 'version': {'type': 'string', 'description': 'Version number, or "current" (the default).'}, 'framework': {'enum': ['next', 'express'], 'type': 'string', 'description': 'Return a ready-to-paste handler scaffold instead of a bare type. Overrides lang.'}, 'schema_id': {'type': 'string', 'description': 'The schema id.'}}, 'additionalProperties': False}
get_bucket
Fetch one webhook endpoint by id, including its url and inbox_url.
Schéma d’entrée
{'type': 'object', 'required': ['bucket_id'], 'properties': {'bucket_id': {'type': 'string', 'description': 'The endpoint id.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': ['event_id'], 'properties': {'event_id': {'type': 'string', 'description': 'The event id.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': ['schema_id'], 'properties': {'version': {'type': 'string', 'description': 'Version number, or "current" (the default).'}, 'schema_id': {'type': 'string', 'description': 'The schema id.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': ['bucket_id'], 'properties': {'type': {'type': 'string', 'description': "The provider's own event name, matched exactly (e.g. payment_intent.succeeded)."}, 'provider': {'type': 'string', 'description': 'Filter to a provider attributed at ingest (e.g. stripe, github).'}, 'bucket_id': {'type': 'string', 'description': 'The endpoint id.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': [], 'properties': {'external_ref': {'type': 'string', 'description': 'Return only the bucket with this exact external_ref.'}}, 'additionalProperties': False}
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".
Schéma d’entrée
{'type': 'object', 'required': ['bucket_id'], 'properties': {'limit': {'type': 'number', 'description': 'Max deliveries to return (1–100, default 20).'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor from a previous response.'}, 'source': {'enum': ['rule', 'replay', 'manual_test'], 'type': 'string', 'description': 'Delivery source.'}, 'success': {'type': 'boolean', 'description': 'Filter to succeeded (true) or failed (false) deliveries.'}, 'bucket_id': {'type': 'string', 'description': 'The endpoint id.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': ['bucket_id'], 'properties': {'q': {'type': 'string', 'description': 'Case-insensitive substring search over body/content-type/method/type/labels.'}, 'type': {'type': 'string', 'description': "The provider's own event name, matched exactly."}, 'limit': {'type': 'number', 'description': 'Max events to return (1–100, default 20).'}, 'since': {'type': 'string', 'description': 'Only events at or after this time (ISO 8601 or YYYY-MM-DD).'}, 'until': {'type': 'string', 'description': 'Only events at or before this time.'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor from a previous response.'}, 'method': {'type': 'string', 'description': 'HTTP method (GET, POST, ...).'}, 'provider': {'type': 'string', 'description': 'Filter to a provider (e.g. stripe, github).'}, 'bucket_id': {'type': 'string', 'description': 'The endpoint id.'}, 'signature_valid': {'type': 'boolean', 'description': 'Only events whose signature verification passed/failed.'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': [], 'properties': {'provider': {'type': 'string', 'description': 'Filter to a provider.'}, 'event_type': {'type': 'string', 'description': "The provider's own event name."}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': ['event_id', 'url'], 'properties': {'url': {'type': 'string', 'description': 'Destination URL to send it to.'}, 'body': {'type': 'string', 'description': 'Replacement request body (defaults to the captured body).'}, 'headers': {'type': 'object', 'description': 'Header overrides layered on top of the preserved set.'}, 'event_id': {'type': 'string', 'description': 'The event id to replay.'}, 'resign_with': {'type': 'string', 'description': 'Signing secret to re-sign the payload with (≥16 chars).'}, 'preserve_headers': {'type': 'boolean', 'description': 'Replay the captured headers verbatim (default true).'}, 'signature_header': {'type': 'string', 'description': 'Header name for resign_with (default x-signature).'}}, 'additionalProperties': False}
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.
Schéma d’entrée
{'type': 'object', 'required': ['bucket_id'], 'properties': {'type': {'type': 'string', 'description': 'Only resolve on this event type.'}, 'timeout': {'type': 'number', 'description': 'Seconds to wait (1–55, default 30).'}, 'provider': {'type': 'string', 'description': 'Only resolve on an event from this provider.'}, 'bucket_id': {'type': 'string', 'description': 'The endpoint id.'}}, 'additionalProperties': False}
Historique
Modifications récentes des outils
Ajouté
find_correlation_keys
17 September 2026 12:38
Ajouté
generate_types
17 September 2026 12:38
Ajouté
diff_schema
17 September 2026 12:38
Ajouté
get_schema
17 September 2026 12:38
Ajouté
list_schemas
17 September 2026 12:38
Ajouté
configure_verification
17 September 2026 12:38
Ajouté
list_deliveries
17 September 2026 12:38
Ajouté
forward_bucket
17 September 2026 12:38
Ajouté
replay_event
17 September 2026 12:38
Ajouté
wait_for_event
17 September 2026 12:38
Ajouté
get_event
17 September 2026 12:38
Ajouté
list_events
17 September 2026 12:38
Ajouté
latest_event
17 September 2026 12:38
Ajouté
delete_bucket
17 September 2026 12:38
Ajouté
get_bucket
17 September 2026 12:38
Ajouté
list_buckets
17 September 2026 12:38
Ajouté
create_bucket
17 September 2026 12:38
Découvrir
Serveurs MCP similaires
shiply
now.shiply/shiply
Publishes and manages web applications with SQL databases, serverless functions, domains, email tests, client intake, contracts, …
Fine Structure
ai.finestructure/fine-structure
Builds and hosts full-stack applications from prompts and supports agent communication through WhatsApp and email.
mcp
cloud.redu/mcp
Provisions and manages cloud instances, networks, storage, databases, backups, VPNs, application deployments, and autocoding-agen…
EchoRelay
dev.echorelay/management
Manages a hosted API relay runtime, including projects, endpoints, credentials, publishing, keys, delivery logs, and dead-letter …
Supero
io.github.supero-platform/supero
Builds, validates, publishes, tests, and deploys multi-tenant applications with schemas, CRUD operations, external data connector…
Replicate
io.github.pipeworx-io/replicate
Provides access to Replicate models, versions, collections, hardware, predictions, and deployments for running and managing hoste…
Relin
io.github.earonesty/relin
Configures webhook sources and destinations, monitors delivery health, investigates failures, manages retries, and replays events.
Scalix Cloud
world.scalix/cloud
Provides managed databases, SQL tools, container builds, persistent Linux machines, domains, scheduled functions, storage, and pr…