Source note · Model Context Protocol transports compared
In MCP revision 2025-11-25, a Streamable HTTP client wishing to resume after a disconnection SHOULD issue an HTTP GET to the MCP endpoint with a Last-Event-ID header, and the server MAY replay messages that would have been sent after that event ID on the disconnected stream.
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 revisions 2025-03-26 through 2025-11-25 (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, subsection Resumability and Redelivery, item 2
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-v2025-11-25-resume. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-v2025-11-25-resume
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-v2025-11-25-resume,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-v2025-11-25-resume},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-v2025-11-25-resume},
note = {Source note mcp-transport-differences-v2025-11-25-resume, checked 2026-09-30}
}