Note: SSE Transport is deprecated as of MCP specification version 2025-03-26, replaced by Streamable HTTP.
- Transport: Uses HTTP/1.1 with Server-Sent Events for server-to-client messages and HTTP POST for client-to-server messages MCP FrameworkModelcontextprotocol
- Not WebSockets: MCP SSE uses standard HTTP with Server-Sent Events, not WebSockets or gRPC Transports – Model Context Protocol Specification
- Not HTTP/2 or HTTP/3: Uses standard HTTP/1.1
Why It's Being Replaced
SSE transport has three major limitations:
- No support for resumable streams
- Requires server to maintain long-lived, highly available connections
- Only allows server messages to be delivered via SSE (unidirectional)
Servers typically expose multiple endpoints:
/sse+/messages(legacy SSE)/mcp(new Streamable HTTP)
Specifically, MCP uses JSON-RPC 2.0 as its wire format between clients and servers. For transmission of JSON-RPC messages, it relies on standard transport mechanisms like HTTP+SSE or Streamable HTTP (among stdio — for communication over standard in and standard out on local servers).
Those specialized transport layers are necessary because traditional HTTP’s request-response model is inefficient for real-time AI communication. That is because plain HTTP introduces high overhead and latency due to frequent connection setups. In contrast, MCP requires continuous, low-latency data streams—something HTTP+SSE and Streamable HTTP are designed to handle.
Course: The Complete Model Context Protocol (MCP) Masterclass | Udemy Business
No comments:
Post a Comment