MCP Events
Official MCP extension for discovering and subscribing to external events through polling, streaming, or webhooks, so agents can react without a new user prompt.
At a Glance
About MCP Events
MCP Events is an official Model Context Protocol extension maintained by the Tasks and Events Working Group. It defines how MCP clients discover events exposed by servers, subscribe with filters, and deliver incoming events to an agent runtime. The extension is in Beta, and its defining proposal, SEP-3415, has Final status.
What It Enables
Developers can build agents that react to incoming messages, repository changes, payments, incidents, or other upstream activity. A server describes the events it supports. The client manages subscriptions and decides how incoming events reach the agent. For example, a compatible repository server could notify a client about a new pull request, allowing the runtime to start a review workflow.
Discovery and Delivery
Servers advertise the extension identifier io.modelcontextprotocol/events. Clients call events/list to discover event names, subscription argument schemas, payload schemas, and available delivery modes. Each event type can support one or more modes.
- Poll uses
events/pollto retrieve events at a server-recommended interval. The client manages the polling loop. - Push uses a long-lived
events/streamrequest. Events arrive over Streamable HTTP or stdio while the subscription remains active. - Webhook uses
events/subscribeto register an HTTPS callback. The server sends signed deliveries, with a subscription lifetime negotiated between client and server.
Resuming and Processing Events
Event occurrences carry an identifier, event name, timestamp, payload, and optional cursor. Clients can persist cursors to resume delivery after reconnecting where the event source supports replay. Stable event identifiers support deduplication. A truncation signal tells the client when part of the history is unavailable. Poll and push preserve order within a subscription, while webhook ordering is best-effort.
Adoption and Security
Both client and server must explicitly support the extension. It requires MCP protocol revision 2026-07-28 or later. Developers implement event discovery, delivery, subscription management, and runtime handling in their applications.
Event payloads are treated as untrusted external data. Servers check authorization when subscriptions are created and when events are delivered. Subsequent agent actions pass through normal MCP authorization. Webhook delivery includes signature verification and callback validation requirements.
Community Discussions
Be the first to start a conversation about MCP Events
Share your experience with MCP Events, ask questions, or help others learn from your insights.
Pricing
Open Source
The Events extension repository is available under Apache 2.0. Implementation, hosting, connected services, and model usage may incur separate costs.
- Public extension specification and documentation
- Poll, push, and webhook delivery definitions
- Client and server implementation guidance
Capabilities
Key Features
- Event discovery through events/list
- JSON Schemas for subscription arguments and event payloads
- Polling through events/poll
- Streaming delivery through events/stream
- Webhook subscriptions through events/subscribe
- Cursor-based resumption where replay is supported
- Stable event identifiers for deduplication
- Subscription lifecycle and termination handling
- Notifications when available event types change
- Authorization checks and signed webhook delivery
