{"slug": "mcp-events-becomes-an-official-beta-extension", "title": "MCP Events becomes an official Beta extension", "summary": "The Model Context Protocol project has published an official Events extension, `io.modelcontextprotocol/events`, now in Beta with its specification finalized as SEP-3415 and maintained by the Tasks and Events Working Group. The extension adds parameterized, payload-carrying event subscriptions with opaque cursors for resumption, `truncated: true` signaling when events were skipped, stable `eventId` deduplication, and three optional delivery modes (webhook, push, poll) that client SDKs select by preference. It targets reacting to upstream activity, waking unattended background agents, and filtered streams such as \"P1 incidents for service X,\" while long-running operations the client itself started remain the domain of the Tasks extension.", "body_md": "[ext-events repository](https://github.com/modelcontextprotocol/ext-events)contains the full specification for the official Events extension (\n\n`io.modelcontextprotocol/events`). [SEP-3415](https://modelcontextprotocol.io/seps/3415-events-extension)is Final, and the extension is in Beta. The\n\n[Tasks and Events Working Group](https://modelcontextprotocol.io/community/working-groups/tasks-events)maintains it.\n\n## modelcontextprotocol/ext-events\n\nFull specification and documentation for MCP Events.\n\n## \n\nMCP already has notifications such as `notifications/resources/updated` and the\n`list_changed` family. They don’t cover this use case:\n- **No parameters or payload.** A notification says that a URI or a list\nchanged. It can’t express “a P1 incident was created for service X”, because\nthere are no subscription arguments, no payload schema and no payload.\n- **A live connection is required.** Notifications arrive only on an open`subscriptions/listen` stream. A client that isn’t connected receives nothing.\n- **No resumption.** There is no cursor, so anything that happens during a\ndisconnect is lost, and the client can’t tell that it missed anything.\n\n## \n\n1. \n**Capability negotiation.** The server advertises`io.modelcontextprotocol/events` in its`server/discover` capabilities. The\nclient may declare the same identifier in its per-request capabilities.\n2. \n**Discovery.** The client calls`events/list` . Each event type has a`name` ,\nan`inputSchema` for subscription arguments, a`payloadSchema` for the data\nit delivers, and the`delivery` modes it supports.\n3. \n**Subscription.** The client subscribes with an event name and arguments,\nusing one of the modes the event type lists. A`null` cursor means “start\nfrom now”.\n4. \n**Delivery.** Each event arrives as an occurrence:`{eventId, name, timestamp, data, cursor}` . The client stores the cursor\nafter each delivery.\n5. \n**Resumption.** After a disconnect or a restart, the client resubscribes\nwith its stored cursor. If the server can’t serve from that position, it\nsays so with`truncated: true` , so the client knows that events were skipped.\n6. \n**Reaction.** The client SDK hands each event to the agent runtime, which\ndecides how to react, for example by starting a new agent turn.\n\n## \n\nNone of the three modes is mandatory. An event type lists any non-empty subset\nof them, and the client SDK picks one it can use.\nSDKs typically prefer webhook when the client has a callback endpoint, then\npush, then poll. A client can override the choice per subscription.\n\n## \n\nEvents are a good fit when your use case involves:\n**Reacting to upstream activity.** New messages, repository pushes, payments, incidents or calendar changes that an agent should act on.\n\n**Unattended agents.** Background agents that run when no user is present and need to be woken by something happening.\n\n**Filtered streams.** Subscriptions that narrow a large stream with arguments, such as “P1 incidents for service X” or “email from this sender”. If the client is waiting for the result of a long-running operation it started itself, use\n\n[Tasks](https://modelcontextprotocol.io/extensions/tasks/overview)instead.\n\n## \n\nCursors are opaque, server-defined positions in the event stream. They make\ndelivery at-least-once when the upstream is durable and the client resumes from\nits last cursor.\n- **Replay is optional per event type.** A server returns`cursor: null` for an\nevent type that has no addressable history. The client then always starts\nfrom now, and accepts that events during a gap can’t be recovered.\n- **Bounded replay.** A client can pass`maxAgeMs` with a stale cursor, so that\na host that was offline for a week gets at most, say, the last five minutes.\n- **Deduplication.**`eventId` is stable for an upstream event, so a client can\ndiscard duplicates within a subscription.\n- **Ordering.** Poll and push deliver events in order within a subscription.\nWebhook ordering is best-effort, and the`timestamp` field orders events.\n\n## \n\n- **Payloads are untrusted data.** Event payloads come from external systems\nand can carry prompt injection. Treat them like tool results, and sanitize or\nsandbox them before they reach a model.\n- **Minimal payloads.** Servers should send enough to identify and triage an\nevent, such as a sender, subject and ID, and let the client fetch full content\nwith tools.\n- **Authorization at every step.** The server checks permission at subscribe\ntime, re-checks at delivery time, and terminates the subscription if access is\nrevoked. Receiving an event never authorizes the agent to act: its follow-up\ntool calls go through normal MCP authorization.\n- **Webhook hardening.** Deliveries are signed with[Standard Webhooks](https://www.standardwebhooks.com/) HMAC signatures.\nCallback URLs must be`https` , the server verifies an endpoint before it\ndelivers to it, and it validates destination IPs to prevent SSRF.\n\n## \n\n### \n\n1\n\nDeclare support\n\nInclude the extension in the per-request capabilities you send:Don’t send \n\n`events/*` requests to a server that hasn’t advertised the extension.\n2\n\nDiscover and subscribe\n\nCall \n\n`events/list`, validate subscription arguments against each event type’s\n`inputSchema`, and pick a delivery mode from its `delivery` list.\n3\n\nPersist cursors\n\nStore the latest cursor for each subscription durably, and resume from it after\na restart. Treat \n\n`truncated: true` as a possible gap, and re-read authoritative\nstate with tools if it matters.\n4\n\nDeliver events safely\n\nDeduplicate by \n\n`eventId`, and treat payloads as untrusted before passing them\nto a model.\n### \n\n1\n\nAdvertise support\n\nInclude the extension in your \n\n`server/discover` capabilities. Set `listChanged`\nif you send `notifications/events/list_changed`:\n2\n\nDescribe event types\n\nReturn each event type from \n\n`events/list` with its `inputSchema`,\n`payloadSchema` and supported `delivery` modes. Evolve schemas additively, and\npublish a breaking change under a new event name.\n3\n\nUse upstream identifiers\n\nUse the upstream system’s stable event ID as \n\n`eventId`, and encode the upstream\nposition in the cursor, so that clients can resume and deduplicate.\n4\n\nCheck authorization\n\nVerify that the principal may subscribe with the given arguments, and terminate\nsubscriptions when access is revoked.\n\n## \n\nMCP Events is an extension to the \n\n[core MCP specification](https://modelcontextprotocol.io/specification/latest). It requires protocol revision`2026-07-28` or later.\n[client matrix](https://modelcontextprotocol.io/extensions/client-matrix)for extension support across clients. Events requires explicit opt-in from both client and server.\n\n## \n\nThe Events extension is specified in the\n[ext-events repository](https://github.com/modelcontextprotocol/ext-events). It uses the standard MCP\n\n[extension negotiation](https://modelcontextprotocol.io/extensions/overview#negotiation)mechanism. For the design rationale, see\n\n[SEP-3415](https://modelcontextprotocol.io/seps/3415-events-extension).", "url": "https://wpnews.pro/news/mcp-events-becomes-an-official-beta-extension", "canonical_source": "https://modelcontextprotocol.io/extensions/events/overview", "published_at": "2026-11-19 00:00:00+00:00", "updated_at": "2026-11-21 20:45:11.851256+00:00", "lang": "en", "topics": ["agent-protocols", "ai-agents", "developer-tools", "ai-tools"], "entities": ["Model Context Protocol", "io.modelcontextprotocol/events", "SEP-3415", "Tasks and Events Working Group", "modelcontextprotocol/ext-events"], "also_reported_by": [], "takeaway": "MCP clients can now subscribe to typed events with arguments and payloads, store the returned cursor after each delivery, and resubscribe from it after a disconnect — treating `truncated: true` as a signal that events were skipped.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/mcp-events-becomes-an-official-beta-extension", "markdown": "https://wpnews.pro/news/mcp-events-becomes-an-official-beta-extension.md", "text": "https://wpnews.pro/news/mcp-events-becomes-an-official-beta-extension.txt", "jsonld": "https://wpnews.pro/news/mcp-events-becomes-an-official-beta-extension.jsonld"}}