Webhook MCP Server (@webhooks-cc/mcp)

claude mcp add -s user webhooks-cc -e WHK_API_KEY=whcc_... -- npx -y @webhooks-cc/mcp

npx @webhooks-cc/mcp setup cursor --api-key whcc_...

npx @webhooks-cc/mcp setup vscode --api-key whcc_...

codex mcp add webhooks-cc -e WHK_API_KEY=whcc_... -- npx -y @webhooks-cc/mcp

npx @webhooks-cc/mcp setup windsurf --api-key whcc_...

npx @webhooks-cc/mcp setup claude-desktop --api-key whcc_...

{
  "mcpServers": {
    "webhooks-cc": {
      "command": "npx",
      "args": ["-y", "@webhooks-cc/mcp"],
      "env": {
        "WHK_API_KEY": "whcc_..."
      }
    }
  }
}

Registry and client support

@webhooks-cc/mcp is published on npm and indexed in the Model Context Protocol ecosystem so AI coding agents can discover and install it directly:

• npm package: @webhooks-cc/mcp (npx -y @webhooks-cc/mcp)
• Official MCP Registry: io.github.webhooks-cc/mcp (server.json schema validated in CI)
• Glama & Smithery: Ships with glama.json metadata and stdio transport support for zero-config inspection
• Supported MCP clients: Claude Code (claude mcp add webhooks -- npx -y @webhooks-cc/mcp), Cursor, VS Code (GitHub Copilot), OpenAI Codex, Windsurf, and Claude Desktop

Available tools

The MCP server exposes 38 tools your AI agent can call. Without an API key, 10 sandbox tools are available (see below).

Provider-aware testing

Agents can inspect provider metadata, send realistic templates, then read the captured request with the provider and event visible in the dashboard.

You: "List the Typeform webhook templates and send a form_response to my endpoint"
Agent: [calls list_provider_templates with provider: "typeform"]
Agent: [calls send_webhook with provider: "typeform", template: "form_response", secret: "..."]
Agent: Captured POST request detected as Typeform / form_response

The same flow works for Stripe, GitHub, Shopify, Twilio, Slack, Paddle, Linear, SendGrid templates, Clerk, Discord templates, Vercel, GitLab, Typeform, Standard Webhooks, DocuSign, Adyen, PayPal templates, and Plaid templates.

For provider templates in send_webhook, secret is required for every signed provider (only sendgrid, discord, and plaid templates are unsigned and need no secret). The MCP server does not inject a default secret.

Endpoint management

Sending and testing

Request management

Request analysis

Emails

Every endpoint receives email at {slug}@mailhooks.cc, and at {slug}+{tag}@mailhooks.cc for any tag.

Forwarding

Teams

Utilities

Without an API key: the agent sandbox

Started without WHK_API_KEY, the server still works. It offers create_endpoint, list_endpoints, get_endpoint, delete_endpoint, list_requests, get_request and wait_for_request with the same names and arguments as above, backed by the agent sandbox: up to 3 temporary endpoints, 25 captured requests each and 100 in all, for 24 hours. The first create_endpoint registers the sandbox, which takes a few seconds of proof of work.

To get everything else, the agent connects to your account: connect_account with your email returns a link and a 6-digit code, you sign in (or sign up) and enter the code, and wait_for_connection then swaps in the full tool set for your account, sandbox endpoints included. about_sandbox explains the limits without a network call. The connection lasts while the server runs; for a lasting setup, create an API key and set WHK_API_KEY.

Prompts

The MCP server provides 3 prompt templates for common workflows:

• debug_webhook_delivery: diagnose why webhook delivery is failing or missing
• setup_provider_testing: set up webhook testing for a specific provider
• compare_webhook_attempts: compare two webhook deliveries or retries

Resources

Three resources provide read-only access to your webhook data:

• endpoints-overview (webhooks://endpoints): all endpoints with recent activity
• endpoint-recent-requests (webhooks://endpoint/{slug}/recent): last 10 requests at an endpoint
• request-details (webhooks://request/{id}): full details of a specific request

Resources return emails without the raw message or the HTML part, like the request tools.

Example conversation

With the MCP server connected, you can talk to your AI agent naturally:

You: "Create a webhook endpoint for testing Stripe"
Agent: Created endpoint "stripe-test" at https://go.webhooks.cc/w/abc123
 
You: "Set it to return 201 with {"received": true}"
Agent: Updated mock response for stripe-test
 
You: "Send a Stripe checkout.session.completed template webhook to stripe-test"
Agent: Sent signed Stripe template to stripe-test
 
You: "Show me what was captured"
Agent: 1 request captured:
  POST /w/abc123 - stripe-signature + checkout.session.completed payload
 
You: "Replay that to my local server"
Agent: Replayed to http://localhost:3000/webhooks - got 200 OK

Learn more