Transports - MCP specification revision 2025-11-25

Publisher

Model Context Protocol project

URL

https://modelcontextprotocol.io/specification/2025-11-25/basic/transports

Published

2025-11-25

Updated

unknown

Accessed

2026-09-30

HTTP status

200

License

not stated on the page; not verified; no-redistribution; short excerpts and locators only

Source notes citing this source

• MCP revisions 2024-11-05, 2025-03-26, 2025-06-18 and 2025-11-25 each state that clients SHOULD support stdio whenever possible. in context
• In MCP revision 2025-11-25, a Streamable HTTP disconnection SHOULD NOT be interpreted as the client cancelling its request, and to cancel the client SHOULD explicitly send an MCP CancelledNotification. in context
• 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. in context
• 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. in context

Cite this source record

APA

WarmTransfer. (2025, November 25). Transports - MCP specification revision 2025-11-25. WarmTransfer. https://warmtransfer.net/knowledge/sources/mcp-spec-2025-11-25-transports

BibTeX

@misc{warmtransfer-mcp-spec-2025-11-25-transports,
  title  = {Transports - MCP specification revision 2025-11-25},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/mcp-spec-2025-11-25-transports},
  note   = {Model Context Protocol project, accessed 2026-09-30}
}