MCP Events bridge

Name: MCP Events bridge
Author: hookdeck

by hookdeckversion 0.10.0i★ –iRuns on your computer

Registry nameio.github.hookdeck/mcp-events-bridge

Install

Overview

Description from the maker (original English)

Turn webhooks into MCP Events that AI agents subscribe to, with Hookdeck Event Gateway.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: Streamable HTTP
Category: Other
You need to fill in: HOOKDECK_API_KEY, HOOKDECK_SIGNING_SECRET, BRIDGE_MCP_SECRET, RESEND_API_KEY, GITHUB_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: HOOKDECK_API_KEY, HOOKDECK_SIGNING_SECRET, BRIDGE_MCP_SECRET, BRIDGE_PORT, RESEND_API_KEY, GITHUB_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "events-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@hookdeck/mcp-events-bridge",
        "serve"
      ],
      "env": {
        "HOOKDECK_API_KEY": "your-value",
        "HOOKDECK_SIGNING_SECRET": "your-value",
        "BRIDGE_MCP_SECRET": "your-value",
        "BRIDGE_PORT": "your-value",
        "RESEND_API_KEY": "your-value",
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add events-bridge --env HOOKDECK_API_KEY=your-value --env HOOKDECK_SIGNING_SECRET=your-value --env BRIDGE_MCP_SECRET=your-value --env BRIDGE_PORT=your-value --env RESEND_API_KEY=your-value --env GITHUB_TOKEN=your-value -- npx -y @hookdeck/mcp-events-bridge serve

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "events-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@hookdeck/mcp-events-bridge",
        "serve"
      ],
      "env": {
        "HOOKDECK_API_KEY": "your-value",
        "HOOKDECK_SIGNING_SECRET": "your-value",
        "BRIDGE_MCP_SECRET": "your-value",
        "BRIDGE_PORT": "your-value",
        "RESEND_API_KEY": "your-value",
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "events-bridge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@hookdeck/mcp-events-bridge",
        "serve"
      ],
      "env": {
        "HOOKDECK_API_KEY": "your-value",
        "HOOKDECK_SIGNING_SECRET": "your-value",
        "BRIDGE_MCP_SECRET": "your-value",
        "BRIDGE_PORT": "your-value",
        "RESEND_API_KEY": "your-value",
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

HOOKDECK_API_KEY secret required env
API key of the Hookdeck project the bridge uses (project settings, Secrets).
HOOKDECK_SIGNING_SECRET secret required env
Signing secret of the same Hookdeck project. Verifies Event Gateway's notifications to the bridge.
BRIDGE_MCP_SECRET secret required env
The MCP endpoint's secret. `setup` generates one on its first run.
BRIDGE_PORT env
Port the bridge listens on.
RESEND_API_KEY secret env
For the Resend source (inbound email). Needs permission to create webhooks.
GITHUB_TOKEN secret env
For the GitHub source in automatic mode. Fine-grained token with Webhooks (read and write). Only `setup` uses it.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account hookdeck, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32568 servers in this category
Published to the registry more recently than 96% of the other 32568 servers in this category
Basic checks equal to or better than 100% of the other 32568 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Events bridge safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: HOOKDECK_API_KEY, HOOKDECK_SIGNING_SECRET, BRIDGE_MCP_SECRET, RESEND_API_KEY, GITHUB_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.10.0) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

FlyDocs

by flydocs.ai

Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

MCP Events bridge

Turn webhooks into MCP Events, so AI agents can act the moment something happens: an email arrives, an issue is opened, a workflow fails. Hookdeck Event Gateway receives, verifies and delivers every event.

For example, an email arrives at a Resend address, and ChatGPT, subscribed through the bridge, acts on it:

Why

MCP Events is an experimental MCP extension that lets an agent subscribe to events instead of polling for them, and ChatGPT supports it. But an agent can only subscribe to MCP servers that implement it, and almost none do yet, while nearly every service already sends webhooks.

The bridge closes that gap:

Webhooks become MCP Events. Sources: Resend inbound email, GitHub, any of 163 Event Gateway source types (Stripe, Slack, Shopify and more), and webhooks from any HTTP sender, such as a service you've built, verified with HMAC, Standard Webhooks, Basic auth or an API key. Add others with defineSource.
Subscribers choose what wakes them. Events have filters, such as an email's sender, or a GitHub repository and action.
Every event verified, delivered and recorded. Event Gateway verifies each service's signatures, retries failed deliveries, drops duplicates within an hour, and keeps a record of every event and attempt.
Stateless. Each subscription is an Event Gateway connection, so there's no database.

It's for developers who want agents (ChatGPT, Claude Code, Hermes Agent and others) to react to events from the services they already use.

Status: 0.9, an open-source project. MCP Events is experimental, and this package may change with it. We're building the same thing into Hookdeck Event Gateway, so tell us what you need. See docs/PLAN.md for what's done and what's next, and CHANGELOG.md for changes between versions. Upgrading from 0.7: see docs/UPGRADING.md.

How it works

Event Gateway verifies each service's webhook signature, keeps every request, turns each one into an MCP Event, and delivers it to each subscriber, signed with the subscriber's secret, with retries.
The bridge is the MCP server: it lists the events on offer, handles subscribe (including the spec's endpoint challenge), and manages one Event Gateway connection per subscription. Events don't pass through it.
The Hookdeck CLI forwards MCP Events to local agents, and Event Gateway's notifications to a bridge on your laptop, so neither needs a public URL of its own.

The design, its trade-offs and how it maps to the spec are in docs/ARCHITECTURE.md.

Supported MCP clients

Clients that support MCP Events subscribe to the bridge, and receive each event as a webhook at their callback URL. Clients that don't, such as Claude Code, poll with the bridge's tools.

Client	How it gets events	Needs a public URL?	Tested	Guide
ChatGPT (Plus or above, Developer mode)	MCP Events, webhook delivery	Yes, for the bridge's MCP endpoint: deploy the bridge, or tunnel to a local one	Yes, end to end	Connect ChatGPT
Claude Code	Polls, with no MCP Events support: `wait_for_event` and `poll_events` during a turn, and the plugin (which runs `watch`) between prompts	No	2.1.294 to 2.1.310	Connect Claude Code
Hermes Agent	MCP Events, webhook delivery	No: a local bridge creates its callback URL	v0.22.5	Hermes Agent guide
Vercel AI SDK (`@ai-sdk/mcp`)	MCP Events, webhook delivery	A callback URL: your own public route, or one a local bridge creates	2.0.84	Library guide
Mastra (`@mastra/mcp`)	MCP Events, poll or webhook delivery	Poll: no. Webhook: a callback URL, as for the Vercel AI SDK	2.5.0	Library guide
TanStack AI (`@tanstack/ai-mcp`)	MCP Events, webhook delivery	A callback URL: your own public route, or one a local bridge creates	1.0.0	Library guide
OpenClaw	MCP Events (beta builds only), webhook delivery	Yes: a bare HTTPS origin, with no path, which a local bridge's callback URLs can't be	Not tested	None yet (openclaw#184684)
Codex	Polls, with `wait_for_event` and `poll_events`	No	codex-cli 0.154.0 (`codex exec`)	Poll clients guide
Cursor's CLI (`cursor-agent`)	Polls, with `wait_for_event` and `poll_events`	No	2026.11.05-86047df (`cursor-agent -p`)	Poll clients guide
Other MCP clients (the Cursor editor's agent, VS Code and others)	Polls, with `wait_for_event` and `poll_events`	No	Not tested	Polling

Versions are the ones tested against the bridge, in October and November 2026. MCP Events support is experimental in Hermes Agent and in the three libraries. Codex and Cursor's CLI were tested non-interactively, and each needs the bridge's tools allowed before it can call them: see the guide.

Set up with a coding agent

The mcp-events-bridge skill walks a coding agent (Claude Code, Cursor, Codex and others that support Agent Skills) through setup, adding sources, connecting an agent and troubleshooting, with a success signal for each step:

npx skills add hookdeck/mcp-events-bridge

Then ask the agent to set up the bridge. It asks you for the credentials. The skill is also in the npm package, under skills/.

Quick start

You need:

Node 22.12 or later.
A Hookdeck account and a project for the bridge. From the project's settings (Secrets): the API key and the signing secret.
The Hookdeck CLI, for running the bridge locally (and for npm run e2e).
At least one source: a Resend or GitHub account, or any service that sends webhooks, including your own.

Create a project and install the bridge:

   mkdir my-bridge && cd my-bridge

npm init -y && npm pkg set type=module npm install @hookdeck/mcp-events-bridge printf 'node_modules/\n.env\n.hookdeck/\n' > .gitignore # .env and .hookdeck/ hold credentials

Choose sources in bridge.config.ts:

   import { defineConfig, env } from '@hookdeck/mcp-events-bridge';

import { github, resend } from '@hookdeck/mcp-events-bridge/sources';

export default defineConfig({ sources: [ resend({ apiKey: env('RESEND_API_KEY') }), // Only setup uses the token, so it's optional here: a deployed bridge runs without it. github({ token: env('GITHUB_TOKEN', { optional: true }), scope: { repos: ['your-org/your-repo'] } }), ], });

Keep only the sources you use, or add others, such as Stripe or your own service: see Sources.

Add credentials to .env:

   HOOKDECK_API_KEY=...

HOOKDECK_SIGNING_SECRET=... RESEND_API_KEY=... # if you use Resend GITHUB_TOKEN=... # if you use GitHub

Create the Event Gateway resources and the webhooks:

   npx mcp-events-bridge setup

The first run generates an MCP secret: add it to .env as BRIDGE_MCP_SECRET. Setup is safe to re-run, and updates the webhooks when you add sources or change events or repositories. A Resend or GitHub webhook deleted at the service is registered again. Removing a source or a repository deletes nothing: delete its webhook (and its Event Gateway source) yourself. Upgrading from 0.7, setup offers to migrate your subscriptions: see docs/UPGRADING.md.

Run the bridge:

   npx mcp-events-bridge serve

Locally, serve checks that setup has run, and starts hookdeck listen for Event Gateway's notifications (which tell the bridge about failing callbacks) and for local agents; it restarts listen if it stops. Events don't pass through the bridge: Event Gateway delivers each one to its subscribers, so none are lost while the bridge is stopped. Once an agent has subscribed, send an email to your Resend address, or open an issue, and its delivery shows under the subscription's connection, mcp-sub- , in the Event Gateway dashboard.

Connect an agent: see Connect ChatGPT, Connect Claude Code, or Supported MCP clients for the others. ChatGPT has to reach the bridge's MCP endpoint, so deploy the bridge, or expose your local port with a tunnel such as cloudflared tunnel --url http://127.0.0.1:8080 and use https:// /mcp/ . Events don't need the tunnel: Event Gateway delivers them to ChatGPT directly.

Connect ChatGPT

With Developer mode on (ChatGPT Plus or above), go to Plugins, choose Add > Create MCP App, paste https:// /mcp/ , and choose No Authentication. ChatGPT can't send an Authorization header (it offers only OAuth or no authentication), so it takes the secret in the URL. Then, in a Work chat, ask to be told about new events, for example emails from a particular sender. ChatGPT subscribes and sets up a monitoring task:

When an event arrives, the task runs with it, as in the screenshot at the top. A chat that's open shows it on its own, about a minute after the event arrives, even though ChatGPT answers the delivery within about 2 seconds (seen on 28 Oct, in an open, focused tab); if it doesn't appear, reload the page. Pausing the task unsubscribes it from the bridge, and resuming it subscribes again from now, with a new callback URL and no cursor, so events that arrive while it's paused aren't delivered or replayed (seen on 27 Oct). They're still in Event Gateway, so ChatGPT can list them with list_events.

ChatGPT keeps the list of events it can subscribe to from when you added the plugin. After you upgrade the bridge or add a source, refresh

Only the beginning is shown; read the rest in the repo

MCP Events bridge

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

FlyDocs

README from the maker

MCP Events bridge

Why

How it works

Supported MCP clients

Set up with a coding agent

Quick start

Connect ChatGPT