Source: https://uptimeify.io/resources/platform-and-support/glossary/streamable-http

# Streamable HTTP

> Streamable HTTP is the HTTP transport for remote [MCP servers](/resources/platform-and-support/glossary/mcp-server): a single endpoint that takes each JSON-RPC message as a POST and answers with either a JSON object or an SSE stream.

Streamable HTTP arrived with protocol revision 2025-03-26 and replaces the older HTTP plus SSE transport from 2024-11-05. Per request, the server decides whether a single response is enough or whether it streams progress notifications over Server-Sent Events before the final result. Revision 2026-07-28 tightens the model further: protocol level sessions and the standalone GET stream are gone, and routing metadata moves into the `Mcp-Method` and `Mcp-Name` headers. A server can then sit behind an ordinary load balancer, with no sticky sessions and no gateway unpacking the request body.