Streamable HTTP changedspecification/2026-07-28/basic/transports/streamable-http
Nearest release: v2.1.305, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 20 Oct 2026 20:02 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+25added
Lines−25removed
From line
13
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 13, old and new numbered
/
from line 13
1313> * Removal of the GET stream endpoint.
1414> * Removal of protocol-level sessions.
1515>
16> See the [changelog](/specification/2026-07-28/changelog) and
16> See the [changelog](/specification/2026-07-28/changelog.md) and
1717> [Backward Compatibility](#backward-compatibility) below.
1818
1919In the **Streamable HTTP** transport, the server operates as an independent
from line 40
4040as the **MCP endpoint**) that supports POST. For example, this could be a URL
4141like `https://example.com/mcp`.
4242
43[http-sse]: /specification/2024-11-05/basic/transports#http-with-sse
43[http-sse]: /specification/2024-11-05/basic/transports.md#http-with-sse
4444
4545[sse]: https://en.wikipedia.org/wiki/Server-sent_events
4646
from line 88
8888> This revision of the core protocol defines no client-to-server
8989> *notifications* over Streamable HTTP. The only client-sent notification in
9090> the core protocol, `notifications/cancelled`, is used only on the
91> [stdio](/specification/2026-07-28/basic/transports/stdio) transport; on
91> [stdio](/specification/2026-07-28/basic/transports/stdio.md) transport; on
9292> Streamable HTTP, closing the SSE response stream is itself the cancellation
9393> signal and no `notifications/cancelled` message is expected (see
9494> \[Cancellation]\[cancellation]). The notification rules above describe the
from line 145
145145
146146Resumable SSE streams via `Last-Event-ID` are not supported.
147147
148[notifications-progress]: /specification/2026-07-28/basic/patterns/progress
148[notifications-progress]: /specification/2026-07-28/basic/patterns/progress.md
149149
150[notifications-message]: /specification/2026-07-28/server/utilities/logging
150[notifications-message]: /specification/2026-07-28/server/utilities/logging.md
151151
152[input-required-result]: /specification/2026-07-28/schema#inputrequiredresult
152[input-required-result]: /specification/2026-07-28/schema.md#inputrequiredresult
153153
154[mrtr]: /specification/2026-07-28/basic/patterns/mrtr
154[mrtr]: /specification/2026-07-28/basic/patterns/mrtr.md
155155
156[sep-2322]: /seps/2322-MRTR
156[sep-2322]: /seps/2322-MRTR.md
157157
158[subscriptions-listen]: /specification/2026-07-28/basic/patterns/subscriptions
158[subscriptions-listen]: /specification/2026-07-28/basic/patterns/subscriptions.md
159159
160160## Message Flow
161161
from line 233
233233any further messages for it. See
234234[Cancellation][cancellation] for the full rules.
235235
236[cancellation]: /specification/2026-07-28/basic/patterns/cancellation
236[cancellation]: /specification/2026-07-28/basic/patterns/cancellation.md
237237
238238## Request Metadata
239239
from line 274
274274server that does not support such clients **MUST** reject a request without
275275the header per [Server Validation](#server-validation).
276276
277[unsupported-version]: /specification/2026-07-28/schema#unsupportedprotocolversionerror
277[unsupported-version]: /specification/2026-07-28/schema.md#unsupportedprotocolversionerror
278278
279[lifecycle-version]: /specification/2026-07-28/basic/versioning#protocol-version-negotiation
279[lifecycle-version]: /specification/2026-07-28/basic/versioning.md#protocol-version-negotiation
280280
281281### Standard Request Headers
282282
from line 361
361361`x-mcp-header` annotations, conforming clients **MUST** mirror the
362362designated parameter values into HTTP headers.
363363
364[tool-definitions]: /specification/2026-07-28/server/tools#x-mcp-header
364[tool-definitions]: /specification/2026-07-28/server/tools.md#x-mcp-header
365365
366366#### Schema Extension
367367
from line 597
597597
598598This error code is allocated from the sub-range the MCP specification
599599reserves for protocol-defined errors. See
600[Error Codes](/specification/2026-07-28/basic/index#error-codes).
600[Error Codes](/specification/2026-07-28/basic/index.md#error-codes).
601601
602602**Example error response:**
603603
from line 678
678678Servers and clients that need to interoperate with counterparts speaking
679679those protocol versions implement the behavior described in the corresponding
680680revision (for example,
681[2025-11-25: Streamable HTTP](/specification/2025-11-25/basic/transports#streamable-http)),
681[2025-11-25: Streamable HTTP](/specification/2025-11-25/basic/transports.md#streamable-http)),
682682in addition to the version-negotiation fallback described above.
683683
684684### HTTP+SSE Transport (2024-11-05)
from line 688
688688> **Deprecated**: The \[HTTP+SSE transport]\[http-sse] from protocol version
689689> 2024-11-05 has been deprecated since protocol version `2025-03-26` and is
690690> classified as Deprecated under the [feature lifecycle
691> policy](/community/feature-lifecycle#deprecating-a-feature)
691> policy](/community/feature-lifecycle.md#deprecating-a-feature)
692692> ([SEP-2596](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2596)).
693693> New implementations **SHOULD NOT** adopt it; existing implementations
694694> **SHOULD** migrate to [Streamable
695> HTTP](/specification/2026-07-28/basic/transports/streamable-http). It is
695> HTTP](/specification/2026-07-28/basic/transports/streamable-http.md). It is
696696> eligible for removal in a future revision; see the [deprecated features
697> registry](/specification/2026-07-28/deprecated).
697> registry](/specification/2026-07-28/deprecated.md).
698698
699699Clients and servers can maintain backward compatibility with the
700700deprecated [HTTP+SSE transport][http-sse] (from
from line 725
725725 server running the old HTTP+SSE transport, and should use that
726726 transport for all subsequent communication.
727727
728[lifecycle-compat]: /specification/2026-07-28/basic/versioning#backward-compatibility-with-initialization-based-versions
728[lifecycle-compat]: /specification/2026-07-28/basic/versioning.md#backward-compatibility-with-initialization-based-versions
729729
No line in this hunk matches that.