# webhook.co [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/webhook-co/webhook  
**GitHub Stars:** 0  
**Views:** 15  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/webhook-co

## Description
Receive, inspect, replay and deliver webhooks — with signature verification and agent triggers.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "webhook-co": {
    "command": "npx",
    "args": ["-y","@webhook-co/cli"]
  }
}
```

## Documentation

## What the webhook.co MCP server does

The webhook.co MCP server exposes webhook.co’s event-capture system to agents over remote HTTP. webhook.co provides permanent signed ingest URLs that receive requests from external services, store each request durably, inspect headers and bodies, and evaluate signatures. Captured events can then be consumed by an agent through MCP.

The MCP surface is intended for inbound event handling. An agent can register a trigger against an endpoint and call `triggers.wait` to drain events after its last cursor. Each returned event includes the verified payload inline when it is within the 64 KiB limit. Events are held durably while the agent is offline, so short polling does not require the agent to remain connected continuously.

Capture order is preserved per endpoint, and delivery to the agent is at least once. Agents should therefore keep track of cursors and design handlers to tolerate repeated events.

## How it works

External providers send requests to a webhook.co ingest URL. The platform records the request before signature verification or deduplication, allowing failed signatures, unknown providers, and downstream failures to remain inspectable. Signature handling supports a registry covering 144 providers, including services such as Stripe, GitHub, Shopify, Slack, Twilio, and others.

The agent connects to `mcp.webhook.co` using the remote MCP surface, which is OAuth-authorized. It creates or uses an endpoint trigger, then polls with `triggers.wait`. This is agent-driven polling rather than a server push: MCP does not provide a native inbound trigger mechanism, so the agent asks for new events when it is ready.

The event stream can include verified payloads, and the durable cursor lets the agent continue from its previous position. webhook.co’s other surfaces include a CLI, REST API, and dashboard, but the MCP interface is focused on agent access to inbound events.

## Setup and configuration

Use the hosted MCP endpoint at `https://mcp.webhook.co` and authenticate through OAuth. The provided material does not specify a local MCP package, a local server command, environment variables, or client-specific configuration examples.

Before an agent can consume events, an endpoint must exist and receive webhooks. Endpoints can be created through the CLI or other webhook.co surfaces. The resulting permanent signed ingest URL can be supplied to services such as Stripe, GitHub, or Shopify. The agent then works with the endpoint’s trigger and cursor rather than directly receiving network callbacks.

Localhost replay is available through the `wbhk` CLI, but it is intentionally not exposed through MCP. Registering replay destinations and subscriptions is also kept outside the MCP surface.

## Tools and capabilities

The documented MCP primitive is:

- `triggers.wait` — waits for and drains new events for a registered endpoint trigger, continuing from the agent’s last cursor.

The webhook.co MCP server supports durable waiting while an agent is offline, capture-order processing per endpoint, at-least-once delivery, and inline verified payloads up to 64 KiB. Signature results distinguish verified, authenticated, failed, and unattempted events at the webhook.co platform level.

MCP does not provide the CLI’s localhost replay operation or the egress-configuring operations for registering destinations and subscriptions. Those restrictions are described as precautions against confused-deputy behavior and SSRF.

## Limitations and notes

The MCP endpoint is remote and OAuth-authorized; the excerpt does not document a local deployment path. `triggers.wait` uses polling initiated by the agent, not push delivery into the agent. At-least-once semantics mean consumers may see duplicates. Payloads are included inline only up to 64 KiB, and the supplied material does not describe behavior for larger payloads.

The webhook.co MCP server is not the interface to every webhook.co feature. Localhost replay remains CLI-only, while replay destinations and subscriptions are configured through other surfaces. No specific compatibility claims are provided for Claude Desktop, Cursor, Windsurf, or Cline.

_Full upstream README: https://allmcps.com/mcp/webhook-co/readme_