Cursor MCP guide

Test webhooks inside Cursor.

Add a project MCP configuration so Cursor can create temporary endpoints and inspect real deliveries while you work on the sender or receiver code.

AnonymousStreamable HTTP8 tools
.cursor/mcp.json
{
  "mcpServers": {
    "webhooktest": {
      "url": "https://webhooktest.net/mcp"
    }
  }
}

Setup and test workflow

01

Create the project configuration

Add the JSON below at .cursor/mcp.json, or enter the URL in Cursor MCP settings. The server is hosted, so no command, environment variable, or package install is required.

02

Reload MCP tools

Reload the window or toggle the server if Cursor does not discover tools immediately. Confirm the server reports eight tools before testing.

03

Keep the capability out of source

Let the agent use the returned bucket ID during the task, but do not commit bucket URLs to fixtures or documentation. Create a fresh bucket for each isolated scenario.

04

Debug from evidence

Trigger the integration and ask Cursor to compare the capture with the implementation. Use the dashboard link when a human-readable payload view is more convenient.

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