MCP setup guide

Use an MCP webhook inspector safely.

A provider-neutral workflow for testing callbacks from an agent: create a scoped endpoint, trigger synthetic data, wait for the delivery, and verify the captured request.

AnonymousStreamable HTTP8 tools
Generic remote-server configuration
{
  "mcpServers": {
    "webhooktest": {
      "url": "https://webhooktest.net/mcp"
    }
  }
}

Setup and test workflow

01

Register the endpoint

Create a remote MCP server entry named webhooktest with the URL shown below. Do not configure a command or bearer token.

02

Create one bucket per scenario

Ask the agent to create a bucket and retain its ID for the current test. The UUID is the capability boundary, so do not paste it into public issues or logs.

03

Use synthetic test data

Point the system under test at the returned webhook_endpoint. Trigger a controlled event that contains no production credentials, payment data, or personal information.

04

Wait, inspect, and compare

Call wait_for_webhook before or just after triggering the sender. Compare method, headers, query values, and body with the provider contract.

05

Clean up explicitly

Use clear_webhooks with confirm:true to reuse the endpoint, or delete_webhook_bucket with confirm:true to remove the bucket and all captures.

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:false is successful; verify the sender used the returned bucket URL.
  • HTTP 429 means the per-IP call, creation, bucket, or concurrent-wait limit was reached.

Client guides

MCP workflowClaudeCursorCodex