What’s actually changing
The specification changelog states it directly:
“Introduced
subscriptions/listenas a single long-lived POST-response stream for opted-in server-to-client change notifications; clients opt into specific types (toolsListChanged,promptsListChanged,resourcesListChanged,resourceSubscriptions)”
The mechanics of a delivered notification are unchanged in shape, still a standard JSON-RPC notification, sent over the stream once a server’s list actually changes:
{
"jsonrpc": "2.0",
"method": "notifications/tools/list_changed"
}What changed is delivery, not payload shape: this notification only arrives if the client opened a subscriptions/listen stream and explicitly opted into toolsListChanged. A client that assumed every notification type arrived automatically, the old SSE behavior, silently stops receiving the types it never opted into.
Structural Comparison Matrix
| Operational Aspect | Before (SSE GET endpoint) | After (subscriptions/listen) |
|---|---|---|
| Delivery default | All notification types, implicitly | Opt-in per type, explicitly |
| Persistence across disconnects | N/A | Subscription lasts only while the stream is open |
| Connection model | Persistent SSE GET | Single long-lived POST-response stream |
Fix it: opt into every type the client actually needs
A silently missing notification is easy to miss
If a client used to react to tools/list_changed without ever explicitly
requesting it, migrating to subscriptions/listen without opting into
toolsListChanged means that handler simply stops firing, with no error to
explain why. Audit every notification type the client logic depends on before
migrating, not just the connection mechanism.
grep -rn "list_changed\|resourceSubscriptions" --include="*.ts" --include="*.py" .For each handler found, confirm the client explicitly opts into the corresponding type (toolsListChanged, promptsListChanged, resourcesListChanged, or resourceSubscriptions) when opening the subscriptions/listen stream, and reopen the stream on disconnect rather than assuming the subscription survives a dropped connection.
Confirmed version
Sourced from the official Model Context Protocol specification changelog, 2026-07-28 revision, published 2026-07-28, including a real notification payload example from the current specification’s tools documentation. Browse more posts like this in the AI Productivity archive.
