# HTTP+SSE Transport

> The old way to reach a remote MCP server. It used two web addresses.

**Field:** Artificial Intelligence  
**Category:** MCP  
**Also known as:** HTTP+SSE, SSE Transport, MCP SSE Transport, Legacy SSE Transport

## Think of it like

It is like talking on two phones. You speak into one and listen on the other.

## Definition

The HTTP+SSE transport is the old way to reach a remote MCP server, from the 2024-11-05 release. The client opened one long stream to hear the server, using server-sent events. It sent its own messages to a second address. It was marked old in 2025-03-26, when Streamable HTTP took its place. New servers should not use it, though some clients still speak it so older servers keep working.

## Example

An older server only offers an /sse address. A new client tries Streamable HTTP first, then falls back to the old SSE transport.

## Why it matters

Many guides and servers still use it. Knowing it is old helps you pick Streamable HTTP for anything new.

## Common mistake

Thinking Streamable HTTP dropped streams. It can still stream; it just needs one address, not two.

## Three principles

- **Two addresses.** One to listen, one to send.
- **Marked old.** Since the 2025-03-26 release.
- **Kept for old servers.** Clients may still fall back.

## Related terms

- [MCP Transport](https://learn.benibix.com/term/ai/mcp-transport)
- [Streamable HTTP Transport](https://learn.benibix.com/term/ai/streamable-http-transport)
- [MCP stdio Transport](https://learn.benibix.com/term/ai/stdio-transport)
- [Server-Sent Events (SSE)](https://learn.benibix.com/term/development/server-sent-events)
- [MCP Protocol Version](https://learn.benibix.com/term/ai/mcp-protocol-version)

## Told apart from

- [HTTP+SSE vs Streamable HTTP](https://learn.benibix.com/compare/http-sse-transport-vs-streamable-http-transport): People think Streamable HTTP got rid of streams, since the old MCP transport it replaced was named after them. It did not. The old HTTP+SSE transport needed two addresses: one long stream to listen and one to send. Streamable HTTP uses one address. A reply can still come back as a stream when it needs to. The change was fewer addresses, not fewer streams.

![A timeline of MCP spec versions named by date. 2024-11-05 uses HTTP plus SSE. 2025-03-26 brings Streamable HTTP and marks HTTP plus SSE as old. 2025-11-25 is the last version with a start-up handshake. 2026-07-28, the current one, puts the version on every request and adds server/discover.](https://learn.benibix.com/diagrams/ai8-mcp-versions.svg)

---

Source: https://learn.benibix.com/term/ai/http-sse-transport
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-18
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
