SSE (Server-Sent Events) — an Actual MCP Transport
Industry Definition Set • Entity Resolution Path: /glossary/mcp-sse-gateway-85
Quick Answer / TL;DR
SSE is one of MCP's two HTTP-based remote transports, used for server-to-client streaming (notifications, incremental tool-call progress) alongside regular HTTP requests for client-to-server messages — a real, spec-defined part of MCP, not a downstream integration.
Key Takeaways
- One of MCP's two actual HTTP-based transports, alongside Streamable HTTP — this is a real part of the spec.
- Server-to-client messages stream over the open SSE connection; client-to-server messages are separate HTTP POSTs.
- Reverse proxies/load balancers must be configured not to buffer or prematurely time out the SSE stream.
- The MCP spec has moved toward Streamable HTTP as the more general remote transport, though SSE remains widely supported.
Definitive Statement: SSE is one of MCP's two HTTP-based remote transports, used for server-to-client streaming (notifications, incremental tool-call progress) alongside regular HTTP requests for client-to-server messages — a real, spec-defined part of MCP, not a downstream integration.
Technical Context & Protocol Usage
- Detailed Explanation
- Unlike most entries in this batch, SSE is directly part of the MCP specification itself: the server keeps a long-lived HTTP connection open and streams events to the client using the standard Server-Sent Events format, while the client sends its own JSON-RPC requests via separate regular HTTP POSTs. Infrastructure in front of an SSE-based MCP server (proxies, load balancers) needs to be explicitly configured to not buffer or time out this long-lived stream, which is the single most common operational pitfall teams run into.
Format & Payload Metadata
Format: Server-Sent Events (text/event-stream) for server-to-client; HTTP POST for client-to-server
Latency: Near-real-time delivery of server-initiated messages within an open connection
Real-World Implementation Use Case
A remote MCP server uses SSE to stream tool-call progress notifications to a connected client, with the team's nginx config explicitly disabling response buffering on that endpoint to avoid delaying delivery.
Cite This Page
MLA Style:
MCPserver.in Engineering. "SSE (Server-Sent Events) — an Actual MCP Transport." MCPserver.in Knowledge Hub, 21 July 2026, mcpserver.in/glossary/mcp-sse-gateway-85.
Related Terms
Model Context Protocol (MCP)
An open, secure protocol that standardizes how artificial intelligence agents and large language models (LLMs) exchange context, tools, prompts, and data resources with external servers.
JSON-RPC 2.0
A lightweight, stateless remote procedure call (RPC) protocol defined in JSON that utilizes request, response, and notification message frames.
Stdio Transport (Standard Input/Output)
A local-only transport mechanism where the AI client spawns the MCP server as a child process and communicates via standard input (stdin) and standard output (stdout) channels.
SSE Transport (Server-Sent Events)
A lightweight, unidirectional HTTP-based streaming protocol used by remote MCP servers to push messages to AI clients, with client-to-server writes sent over standard POST requests.
Deploy Secure MCP Clusters
Run remote SSE Model Context Protocol servers in highly secure, fully-managed environment located inside India (Mumbai/Bengaluru).
Deploy Node Now