Webhook Studio

Registre officiel Autres

Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http webhook-studio 'https://webhook-studio.com/mcp' --header 'Authorization: <Bearer <token>. A keyless read+replay token from POST /api/start (ws_anon_...), or a full-access API key from your dashboard (ws_live_...). See https://webhook-studio.com/mcp/setup>'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "webhook-studio": {
            "type": "http",
            "url": "https://webhook-studio.com/mcp",
            "headers": {
                "Authorization": "<Bearer <token>. A keyless read+replay token from POST /api/start (ws_anon_...), or a full-access API key from your dashboard (ws_live_...). See https://webhook-studio.com/mcp/setup>"
            }
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Webhook Studio
  2. Three jobs, one URL
  3. Use it from your AI tools (MCP)
  4. Tools
  5. Keyless in one call (no MCP client needed)
  6. Provider guides
  7. License

Webhook Studio

A webhook pipeline your agent can drive — keyless. Provision a real endpoint, wait for the provider event, replay it into localhost, forward it to your app, and generate types from your actual captured payloads. Built for humans debugging webhooks and for AI agents building the integration.

→ App: https://webhook-studio.com · Docs: https://webhook-studio.com/docs · Agent spec (llms.txt): https://webhook-studio.com/llms.txt


Three jobs, one URL

  • Debug — a zero-signup endpoint, a live inbox with full headers + raw body, and signature verification results on every request.
  • Route — forward matching events to your backend with AND/OR conditions, and durable re-drive: a delivery interrupted by a crash or deploy is re-driven from a durable record, not silently dropped.
  • Learn — every event updates a durable model of what the provider actually sends your account. Ask for a TypeScript / Zod / JSON-Schema type and the optional fields are the ones genuinely sometimes absent in your traffic; ask what changed between two versions and get a breaking-change diff. No other webhook tool does this. Honest comparison: https://webhook-studio.com/compare

Use it from your AI tools (MCP)

Webhook Studio is a remote MCP server (Streamable HTTP, stateless). Add one URL:

claude mcp add --transport http webhook-studio https://webhook-studio.com/mcp \
  --header "Authorization: Bearer $(curl -s -X POST https://webhook-studio.com/api/start | jq -r .api_token)"

That curl mints a keyless read + replay token (no signup) bound to a fresh 3-day endpoint. For full access — create endpoints, configure verification, stand up forwards — use a ws_live_… key from your dashboard.

Or add it to your client's MCP config (~/.cursor/mcp.json, .vscode/mcp.json, claude_desktop_config.json) — full setup for every client at https://webhook-studio.com/mcp/setup:

{
  "mcpServers": {
    "webhook-studio": {
      "url": "https://webhook-studio.com/mcp",
      "headers": { "Authorization": "Bearer ws_live_your_key_here" }
    }
  }
}

The Authorization header is optional — omit it for a public connection (the read/replay tools that accept a ws_anon_… token), or set a ws_live_… key for the full toolset.

Listed in the official MCP Registry as com.webhook-studio/webhooks. The manifest is server.json in this repo.

Tools

Task-shaped, not resource-shaped — reach for them by intent:

create_bucket · list_buckets · get_bucket · delete_bucketProvision and manage endpoints
latest_event · list_events · get_event · wait_for_eventRead events; block until one arrives
replay_event · forward_bucket · list_deliveriesReplay to localhost, forward, check results
configure_verificationTurn on HMAC with the provider's real secret
list_schemas · get_schema · diff_schema · generate_types · find_correlation_keysThe knowledge layer

Each tool maps 1:1 onto a /v1 REST route, so the REST reference is also the tool reference.

Keyless in one call (no MCP client needed)

curl -X POST https://webhook-studio.com/api/start
# → { ingest_url, inbox_url, api_token: "ws_anon_…", expires_in_days: 3, ... }

Point a provider at ingest_url, hand the human inbox_url, and use api_token to read + replay over /v1 or /mcp. Full agent guide: https://webhook-studio.com/llms.txt

Provider guides

One-click test URLs and correct signature-verification snippets per provider:

License

Documentation and examples in this repo are MIT. The hosted product is proprietary.

Questions fréquentes

Qu'est-ce que Webhook Studio ?

Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.

Comment installer Webhook Studio ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http webhook-studio 'https://webhook-studio.com/mcp' --header 'Authorization: <Bearer <token>. A keyless read+replay token from POST /api/start (ws_anon_...), or a full-access API key from your dashboard (ws_live_...). See https://webhook-studio.com/mcp/setup>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Webhook Studio ?

Oui. Il attend Authorization, à renseigner dans sa configuration.

Webhook Studio est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Webhook Studio ?

Il est publié par lestertww. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.