Skip to main content
Glama
MCP Events Bridge

MCP Events Bridge

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
extensions
{
  "io.modelcontextprotocol/events": {}
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_eventA

Get one past event by its name and eventId, as an MCP Events delivery or list_events gives them, read from Hookdeck Event Gateway. Returns the eventId, name, timestamp and data, the same as its delivery. Use it to look an event up again by id; to browse past events, use list_events, and for new ones, wait_for_event or poll_events. An unknown name, an eventId Event Gateway doesn't have (or no longer keeps), and an event whose source can't be searched by id are errors; for the last, the error says to use list_events.

list_eventsA

List past events, newest first by timestamp, from every source or for one event name, read from Hookdeck Event Gateway. Each has the eventId, name, timestamp and data its delivery has. Use it to look back at what already happened; to follow new events, use wait_for_event or poll_events, and for one event you have the id of, get_event. It reads each source's requests newest first until it has limit events, reading at most 500 per source, so with name on a busy source where few requests are that event it can return fewer than exist. Events Event Gateway no longer keeps aren't listed. An unknown name is an error; for the names, see list_sources or events/list.

list_sourcesA

List the configured sources (the services events come from): each one's id, type, event types and webhook subscription count. Each entry in a source's events is an event type, as events/list describes it: its name, description and inputSchema (the arguments it takes). Use it first, to find the event type names that list_events, get_event, wait_for_event and poll_events take, and the arguments wait_for_event and poll_events take. subscriptions counts webhook subscriptions (events/subscribe); poll subscriptions are held by the client and not counted. For events that already happened, list_events.

poll_eventsA

Get events that happened since your cursor, for clients that can't subscribe with MCP Events (events/subscribe). Same as events/poll. Call it first without a cursor to start from now, then call it again with the cursor it returned: at once when hasMore is true, otherwise after nextPollMs. Events can repeat: dedupe by eventId. truncated: true means some events were skipped (maxAgeMs, or older than Event Gateway keeps). To wait for the next event in one call instead, use wait_for_event. For past events, use list_events.

wait_for_eventA

Wait for the next events after your cursor, returning as soon as there are some, or with none after timeoutMs (default 45 s, at most 50 s). Without a cursor, waits for events from now on. Call it again with the cursor it returns to keep waiting; dedupe by eventId. Uses the same cursor as poll_events and events/poll.

create_callback_urlA

Create a public callback URL for MCP Events webhook delivery, for an agent on this machine with no public URL of its own, then pass it to events/subscribe. Deliveries reach Hookdeck Event Gateway at the URL, and the bridge forwards them to http://localhost:. With secret, Event Gateway answers the subscribe challenge and accepts only deliveries signed with it. Without it, the URL is pass-through and your receiver must verify every delivery: use that when you subscribe with a different secret per path under one URL. Deliveries are signed with your subscription secret: route them by X-MCP-Subscription-Id and dedupe by webhook-id. Calling again with the same agent, name and secret returns the existing URL; a different secret, or a port or path you pass that differs, is an error. A URL no subscription uses for an hour is deleted. Not needed if your agent has a public URL or polls (wait_for_event, poll_events).

list_callback_urlsA

List the callback URLs an agent created with create_callback_url, with each one's local port and path and whether it's pass-through. Check here before creating a URL.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a distinct role: source discovery, new-event polling, long-waiting, past-event listing, single-event lookup, and callback URL creation/listing. The closest pair, poll_events and wait_for_event, is clearly separated by immediate return versus blocking wait and cross-references in the descriptions.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: list_sources, poll_events, wait_for_event, create_callback_url, get_event, list_callback_urls, and list_events. There are no mixed conventions or vague names.

Tool Count5/5

Seven tools is well-scoped for an event bridge: source discovery, event consumption via polling/waiting/past lookup, and callback URL support. Each tool earns its place without redundant surface area.

Completeness4/5

The core event-consumption lifecycle is covered: discover sources, poll or wait for new events, list past events, and retrieve an event by id. Callback URL management is slightly incomplete because URLs can be created and listed but not explicitly deleted, though they auto-expire after an hour.

Maintenance

ActivityNo data
ResponsivenessOutdated data