Debug webhooks with your AI agent

Pipehero ships an MCP server so an agent (Claude Code, Cursor, Claude Desktop) can read and replay your webhooks. Connect it one of two ways:

Remote (no install, recommended)

Add the hosted server by URL. Your client opens the browser to sign in and approve — no token to paste (OAuth).

claude mcp add --transport http pipehero https://mcp.pipehero.app/mcp

For CI/headless, skip OAuth and pass a token from Settings instead:

claude mcp add --transport http pipehero https://mcp.pipehero.app/mcp \
  --header "Authorization: Bearer <token>"

Local (via the CLI)

Runs on your machine, reusing pipehero login:

claude mcp add pipehero -- pipehero mcp

Or add it to any MCP client config:

{ "mcpServers": { "pipehero": { "command": "pipehero", "args": ["mcp"] } } }

Tools

list_tunnelsYour tunnels and whether each is online.

list_requests(subdomain)Recent captured webhooks for a tunnel.

get_request(subdomain, id)Full request + response (headers + body).

replay_request(subdomain, id)Replay a webhook to your localhost.

send_test_webhook(subdomain, …)Fire a test webhook at your tunnel. (Pro)

Why this is powerful: your agent has both the captured webhook (via these tools) and your codebase (in the editor), so it can explain why a handler failed — correlating the exact payload and headers with your code — then fix it and replay to confirm.

Example prompts

›The last webhook to myapp returned 500 — read the payload and my handler and tell me why it failed.
›Fix the handler, then replay the webhook to confirm it works.
›Compare what Stripe sent to what my code expects and flag any mismatch.
›Show me every failed (non-2xx) webhook and what they had in common.
›List my tunnels and which are online.