MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

subscriptions/listen

protocol

subscriptions/listen - The 2026-07-28 replacement (SEP-2575) for the HTTP GET notification stream and resources/subscribe: one long-lived POST-response stream where clients opt in to specific change types (toolsListChanged, promptsListChanged, resourcesListChanged, resourceSubscriptions) and servers tag notifications with a subscription id.

subscriptions/listen is how a stateless protocol still delivers change notifications. Instead of a standing GET stream and per-resource subscribe calls, a client opens one long-lived POST whose response stream carries exactly the notification types it opted into: toolsListChanged, promptsListChanged, resourcesListChanged, and resourceSubscriptions. The server acknowledges and tags each notification with a subscription id. Request-scoped notifications such as progress and log messages stay on the originating request's response stream, keeping the listen stream purely for change signals.

Related concepts

Sources and verification

Last verified · confidence 1.00.

  1. Official 2026-07-28 changelog - "Replace the HTTP GET endpoint and resources/subscribe/resources/unsubscribe with subscriptions/listen: a single long-lived POST-response stream for opted-in server-to-client change notifications", with clients opting into specific types and servers tagging notifications with io.modelcontextprotocol/subscriptionId (SEP-2575) - accessed

← All concepts