Capture, inspect, replay and deliver webhooks. Open source, with a free permanent signed URL, signature verification, and one-command replay to localhost.
Socratic requirement refinement before writing code. Use at the start of a non-trivial feature or change to turn a vague ask into clear, agreed requirements and constraints. Pairs with the /brainstorming command and feeds /feature-dev.
Plan and run safe, reversible Postgres schema and data migrations. Use when adding/altering tables or columns, backfilling data, or changing the data model for the webhook metadata store.
Author developer docs and reference, and keep CLI/API/web/MCP at parity and on-voice. Use when writing or updating docs, API/CLI/MCP reference, quickstarts, or changelogs.
Deploy and operate the Cloudflare-forward webhook stack safely. Use when deploying Workers, Durable Objects, or container-lane services, configuring wrangler/bindings, rolling back, or running production infra changes.
Triage technical issues and bug reports into reproducible, actionable findings. Use when investigating a reported failure in ingestion, delivery, signing, replay, or a surface (CLI/API/web/MCP).
Build interactive MCP UI widgets (forms, pickers, confirmation dialogs, charts, live status) rendered in sandboxed iframes. Use when an MCP tool genuinely needs a visual/interactive surface instead of text. Pairs with build-mcp-server.
Design and scaffold an MCP server for webhook.co. Use when adding or extending the MCP surface (apps/mcp), exposing a capability as MCP tools, or deciding how an MCP server should be deployed and structured.
Package a local stdio MCP server into an installable MCPB bundle. Use only when shipping a server users install and run on their own machine (e.g. alongside the CLI tunnel), not for the Workers-hosted remote server.
A disciplined 4-phase method for debugging in webhook.co — root-cause investigation, pattern analysis, hypothesis testing, then implementation. Use when chasing a bug or unexpected behavior instead of guessing-and-checking. Stop and review architecture after 3 failed fixes.
Strict red-green-refactor TDD for webhook.co. Use when implementing or changing behavior — especially correctness-critical paths (signing/verification, dedup/idempotency, retries, ordering, replay, metering). Tests must fail before any implementation.
Diagnose why an inbound webhook signature fails to verify, and write correct verification code for a named provider. Use when a signature check rejects real traffic, when a webhook works in a provider's test console but not against your server, or when you are implementing verification for Stripe, GitHub, Shopify…