mcpField
O
OpenWebhook

OpenWebhook

Local
openwebhook.coDeveloper Tools
RepositoryVisit website

About OpenWebhook

Inspect webhooks from Cursor or Claude. No account needed. Pro adds permanent slugs

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "co-openwebhook": {
      "command": "npx",
      "args": [
        "-y",
        "openwebhook"
      ],
      "env": {
        "OPENWEBHOOK_TOKEN": "<OPENWEBHOOK_TOKEN>"
      }
    }
  }
}
Run commandnpx -y openwebhook
Environment variables to set
OPENWEBHOOK_TOKENSecretOptional Pro token for permanent slugs. Leave empty for an anonymous inspect URL.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmopenwebhook1.2.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.