openwebhook.co
Open inspector →
developer guide

How to Test Webhooks in Cursor

Add OpenWebhook MCP in Cursor, ask for an inspect URL, watch the stream, and read the next webhook in the agent chat. No account required to start.

By David Lorenzo García··5 min read

Cursor talks to OpenWebhook over MCP. You add openwebhook mcp, the agent prints a public HTTPS URL, and the next request appears in the chat. The tool catalog is on OpenWebhook MCP tools. This page is the Cursor config only.

Prefer a browser tab? Use test webhooks online.

Add the MCP server

Install once, or use npx so Cursor does not need a global binary:

npm install --global openwebhook

Project or user mcp.json:

{
  "mcpServers": {
    "openwebhook": {
      "command": "npx",
      "args": ["-y", "openwebhook", "mcp"]
    }
  }
}

If npx is blocked, set command to the absolute path from which openwebhook and args to ["mcp"]. Restart the agent after saving. Add OPENWEBHOOK_TOKEN in env only for a permanent slug.

Inspect from the chat

Ask: “Give me my OpenWebhook inspect URL and watch for the next webhook.” Then send a request:

curl -X POST \
  'https://hooks.openwebhook.co/YOUR-UUID/cursor' \
  -H 'content-type: application/json' \
  --data '{"from":"cursor"}'

Or paste the URL into GitHub, Stripe, or Zapier. The agent should show method, path, headers, and body. If tools never appear, the MCP server did not start (bad path, or the agent was not restarted).

When to use the CLI

listen --port when your handler is a local HTTP server. MCP when you want the payload in Cursor to draft code.

Related guides