MCP Events extension (beta)
MCP Events is the official Model Context Protocol extension io.modelcontextprotocol/events. It lets an MCP client subscribe to things that happen in an upstream system, such as a new email, a push to a repository, or a production incident, and have an agent react even when no user is present. SEP-3415 is Final and the extension is in Beta, maintained by the Tasks and Events Working Group. A server lists event types with events/list, each with an inputSchema for subscription arguments, a payloadSchema for the data it delivers, and the delivery modes it supports. There are three modes, and none is mandatory: poll (events/poll), push (events/stream), and webhook (events/subscribe, signed per Standard Webhooks). Opaque cursors let a client resume after a disconnect, and truncated: true tells it that events were skipped. The extension is defined for MCP protocol revision 2026-07-28 and later. The MCP extension client matrix does not yet mark Events support for Claude (web), Claude Desktop, or Claude Code.
Soft Pyramid is not affiliated with, endorsed by, or a partner of Anthropic. These guides are Soft Pyramid's own notes on Claude features.
How to use it
- Target MCP protocol revision 2026-07-28 or later. The extension relies on per-request client capabilities, server/discover, and subscriptions/listen, which earlier revisions do not have.
- Server: advertise io.modelcontextprotocol/events in your server/discover capabilities.
- Server: return each event type from events/list with its name, inputSchema, payloadSchema, and supported delivery modes.
- Client: you may declare the same identifier in your per-request capabilities. Call events/list, then subscribe with an event name, arguments, and one of the modes that event type lists. A null cursor means start from now.
- Client: store the cursor after each delivery, and resubscribe with it after a disconnect or restart.
- Treat event payloads as untrusted data.
