webhooksdeveloper-toolsmcpevent-delivery
Receives, verifies, stores, replays, and delivers webhooks through a remote MCP endpoint.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
We couldn’t automatically confirm this listing starts correctly
We ran the install command below but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.
npx -y @webhook-co/cliNo response to initialize.
This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.
Manual Client & Custom JSON ConfigExpand JSON â–¾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Capture provider webhooks for agent workflows
Poll durable event triggers from an agent
Resume event processing after agent downtime
Inspect verified webhook payloads within an MCP workflow
Key features
Remote HTTP MCP endpoint
OAuth authorization
Durable endpoint triggers
At-least-once event delivery
Capture-order processing per endpoint
Inline verified payloads up to 64 KiB
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Webhook.co.
Extracted Tool Capabilities
Remote HTTP MCP endpoint
OAuth authorization
Durable endpoint triggers
At-least-once event delivery
Capture-order processing per endpoint
Inline verified payloads up to 64 KiB
How Webhook.co works
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.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
Last commit
8d ago
Most recent push to the default branch.
Install check
Inconclusive
Didn't respond in our test window — often a slow first install.
Directory activity
15 views
Config copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Webhook.co
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/webhook-co)HTML Embed
<a href="https://allmcps.com/mcp/webhook-co"><img src="https://allmcps.com/api/badge/webhook-co?style=directory" alt="Webhook.co on AllMCPs" /></a>Technical Specs & Signals
CategoryCommunication
PricingFree
96/96 checks healthy over the last 3d
43Quality signal: Fair · 43/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools17/30
Adoption & activity4/15
Community engagement1/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 2d ago via OSV.dev · @webhook-co/cli (npm)
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.