Skip to content
BENIBIX Learn

HTTP+SSE Transport

AI🔌 MCPTransports and Authorization

Also known as HTTP+SSE, SSE Transport, MCP SSE Transport, Legacy SSE Transport

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

Think of it like

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

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.

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.
HTTP plus SSE came first, and Streamable HTTP replaced it in 2025-03-26.

Common mistake

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

Key takeaways

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

Compare