Source note · Model Context Protocol transports compared
In MCP revision 2025-11-25, the Streamable HTTP MCP endpoint MUST support both POST and GET, the client MAY open a standalone SSE stream with HTTP GET, and the server MAY assign a session ID in an MCP-Session-Id header on the response containing the InitializeResult, which the client MUST then include on all subsequent HTTP requests.
Checked 2026-09-30
- Vendor
- Model Context Protocol project
- Product
- MCP specification
- Subsystem
- Streamable HTTP transport
- Deployment
- remote-http
- Region
- not restricted
- Release range
- MCP revision 2025-11-25 only (legacy)
- Checked
- 2026-09-30
Sources
- Transports - MCP specification revision 2025-11-25 — Model Context Protocol project · tier 1 standards and regulators · section Streamable HTTP, introduction; subsections Listening for Messages from the Server and Session Management
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-v2025-11-25-http-shape. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-v2025-11-25-http-shape
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-v2025-11-25-http-shape,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-v2025-11-25-http-shape},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-v2025-11-25-http-shape},
note = {Source note mcp-transport-differences-v2025-11-25-http-shape, checked 2026-09-30}
}