MCP Events bridge runs on your own machine — the client starts it, so there is no endpoint to ping. 601 installs a week from npm. Last commit 5 Nov 2026.
Turn webhooks into MCP Events that AI agents subscribe to, with Hookdeck Event Gateway.
Nothing serious here today
Today is the operative word: we check MCP Events bridge every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-events-bridge -e 'HOOKDECK_API_KEY=<HOOKDECK_API_KEY>' -e 'HOOKDECK_SIGNING_SECRET=<HOOKDECK_SIGNING_SECRET>' -e 'BRIDGE_MCP_SECRET=<BRIDGE_MCP_SECRET>' -- npx -y @hookdeck/mcp-events-bridge{
"mcpServers": {
"mcp-events-bridge": {
"command": "npx",
"args": [
"-y",
"@hookdeck/mcp-events-bridge"
],
"env": {
"BRIDGE_MCP_SECRET": "<BRIDGE_MCP_SECRET>",
"HOOKDECK_API_KEY": "<HOOKDECK_API_KEY>",
"HOOKDECK_SIGNING_SECRET": "<HOOKDECK_SIGNING_SECRET>"
}
}
}
}[mcp_servers.mcp-events-bridge]
command = "npx"
args = ["-y", "@hookdeck/mcp-events-bridge"]
env = { HOOKDECK_API_KEY = "<HOOKDECK_API_KEY>", HOOKDECK_SIGNING_SECRET = "<HOOKDECK_SIGNING_SECRET>", BRIDGE_MCP_SECRET = "<BRIDGE_MCP_SECRET>" }{
"mcpServers": {
"mcp-events-bridge": {
"command": "npx",
"args": [
"-y",
"@hookdeck/mcp-events-bridge"
],
"env": {
"BRIDGE_MCP_SECRET": "<BRIDGE_MCP_SECRET>",
"HOOKDECK_API_KEY": "<HOOKDECK_API_KEY>",
"HOOKDECK_SIGNING_SECRET": "<HOOKDECK_SIGNING_SECRET>"
}
}
}
}{
"servers": {
"mcp-events-bridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hookdeck/mcp-events-bridge"
],
"env": {
"BRIDGE_MCP_SECRET": "<BRIDGE_MCP_SECRET>",
"HOOKDECK_API_KEY": "<HOOKDECK_API_KEY>",
"HOOKDECK_SIGNING_SECRET": "<HOOKDECK_SIGNING_SECRET>"
}
}
}
}Put your own values in place of
<HOOKDECK_API_KEY> (API key of the Hookdeck project the bridge uses (project settings, Secrets)), <HOOKDECK_SIGNING_SECRET> (Signing secret of the same Hookdeck project. Verifies Event Gateway's notifications to the bridge), <BRIDGE_MCP_SECRET> (The MCP endpoint's secret. `setup` generates one on its first run).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
BRIDGE_PORT (Port the bridge listens on), RESEND_API_KEY (For the Resend source (inbound email). Needs permission to create webhooks), GITHUB_TOKEN (For the GitHub source in automatic mode. Fine-grained token with Webhooks (read and write). Only `setup` uses it).
Alternatives to MCP Events bridge
same job, measured the same wayApache Camel API Gateway with REST-to-MCP bridging for LLM agents.
Turn this machine into a webhook endpoint that runs Agent Skills with Claude Code or Codex.
Local QEMU VM manager with opt-in MCP event subscriptions for AI agents.
Local MCP gateway that proxies AI clients to many MCP servers with a token-efficient code mode
MCP server for subscribing to and managing on-chain event webhooks via Crypto APIs
A2A v1.0.1 agents as MCP 2026-07-28 tools, with the tasks extension
Self-hosted AI gateway that governs MCP servers, LLM traffic, and A2A agents behind one endpoint
21 tools for AI agents to manage BTCPay Server: invoices, payments, stores, webhooks, Lightning
MCP Events bridge — questions
Answers built from our own checks of this server.