What is SSE Transport?
SSE Transport is an HTTP-based Model Context Protocol transport pattern that uses Server-Sent Events to deliver server-to-client messages while requests are sent through HTTP endpoints.
Quick Facts
| Specification | Official Specification |
|---|
How It Works
SSE Transport is used when an MCP integration needs a network-accessible server rather than a local stdio process. Server-Sent Events provide a one-way event stream from server to client, while client requests are typically sent through HTTP. This model is more suitable for remote or shared services, but it introduces security and operations concerns that local stdio does not: authentication, authorization, TLS, tenant isolation, timeouts, connection limits, load balancing, and observability.
Key Characteristics
- HTTP-based remote transport: supports MCP servers that are not local child processes
- Event stream delivery: uses Server-Sent Events for server-to-client notifications and responses
- Network security requirement: needs TLS, authentication, authorization, and request validation
- Operational complexity: must handle reconnects, load balancing, connection limits, and idle timeouts
- Service-oriented fit: appropriate for shared enterprise MCP servers or hosted integrations
Common Use Cases
- Connecting an AI host to a remote enterprise knowledge MCP Server
- Serving one managed MCP integration to many clients
- Deploying MCP capabilities behind corporate authentication and network controls
- Streaming server notifications back to an AI application over HTTP
- Operating MCP servers where local process execution is not practical
Example
Loading code...Frequently Asked Questions
When should SSE Transport be used?
Use it when the MCP server must run as a remote service, be shared across clients, or sit behind enterprise authentication. For local desktop or IDE tools, stdio is usually simpler.
Is SSE bidirectional?
SSE itself is server-to-client. In MCP-style HTTP transports, client-to-server requests are typically sent through separate HTTP endpoints while SSE carries server events back.
What security controls does SSE Transport need?
It needs TLS, authentication, authorization, tenant isolation, input validation, rate limits, logging, and careful handling of sensitive data in event streams.
What operational issues are common with SSE?
Common issues include proxy buffering, idle connection timeouts, reconnect storms, load-balancer stickiness, missing heartbeats, and insufficient observability for long-lived streams.