MCP Events
A draft extension to the MCP protocol that introduces the capability for servers to proactively push events to clients. It expands the interaction model from unidirectional request-response to bidirectional subscription-based push, supporting use cases such as monitoring alerts, data updates, and task-completion callbacks.
Timeline (last 90 days)
ChatGPT is adding draft support for MCP Events, allowing MCP servers to proactively push events to clients.
The core argument put forward in the article is that a subscription is essentially a credential, because it grants an external system ongoing permission to proactively reach a user's session in the future.
A subscription, as a continuously valid authorization, should be managed as a credential, requiring a clear holder, scope, lifecycle, and a mechanism by which it can be revoked.
A common industry solution for credential revocation is 'short window + strong validation': setting extremely short token expiration times while querying an authoritative state source in real time before each push to verify subscription validity.
MCP Events is still in the draft stage.
All Facts (5)
The core argument put forward in the article is that a subscription is essentially a credential, because it grants an external system ongoing permission to proactively reach a user's session in the future.
50%UnverifiedA subscription, as a continuously valid authorization, should be managed as a credential, requiring a clear holder, scope, lifecycle, and a mechanism by which it can be revoked.
50%UnverifiedA common industry solution for credential revocation is 'short window + strong validation': setting extremely short token expiration times while querying an authoritative state source in real time before each push to verify subscription validity.
50%UnverifiedMCP Events is still in the draft stage.
50%UnverifiedChatGPT is adding draft support for MCP Events, allowing MCP servers to proactively push events to clients.
50%