Add the HTTP server
Run the command below in Claude Code. For Claude clients with an MCP settings screen, add the same URL as a remote HTTP server named webhooktest.
Claude MCP guide
Test webhooks from Claude.
Connect the hosted MCP server over HTTP, ask Claude to create an endpoint, trigger your integration, and let Claude inspect the captured request.
AnonymousStreamable HTTP8 tools
Claude Code
claude mcp add --transport http webhooktest https://webhooktest.net/mcpSetup and test workflow
Confirm tool discovery
Start a fresh session if necessary and ask Claude to list the webhook tools. You should see create, get, list, wait, configure, clear, and delete operations.
Run the delivery test
Ask Claude to create a bucket and wait for a webhook. Trigger the sender with the returned endpoint, then ask Claude to explain any mismatch in headers or payload shape.
Test failure handling
Have Claude configure a non-2xx response, trigger the sender again, and inspect whether it retries according to your expected policy.
What the server exposes
Create and understand
`create_webhook_bucket` creates a temporary endpoint; `get_webhook_bucket` reads its name and response settings.
Observe deliveries
`wait_for_webhook` waits up to 25 seconds; `list_webhooks` paginates summaries; `get_webhook` returns one scoped capture.
Control and clean up
`configure_webhook_response` changes the reply. `clear_webhooks` and `delete_webhook_bucket` require explicit confirmation.
Privacy and limits
Authorization, cookie, API-key, token, secret, password, and signature-like header or query values are redacted by default. Agents must explicitly request sensitive values. Bodies are limited to 64 KiB in tool output by default and can be raised only to 256 KiB. Use synthetic data: the endpoint is a debugging service, not a production processor.
Troubleshooting
- Use the exact HTTPS URL and select remote or Streamable HTTP transport.
- Restart or reload the client after changing MCP configuration.
- Check that corporate policy allows the endpoint and outbound HTTPS.
- A timeout with
received:falseis successful; verify the sender used the returned bucket URL. - HTTP 429 means the per-IP call, creation, bucket, or concurrent-wait limit was reached.