---
type: Glossary Term
title: "Streamable HTTP"
description: "Streamable HTTP is the primary remote transport for the Model Context Protocol (MCP), replacing the early dual-endpoint HTTP+SSE transport from the 2024-11-05 specification."
resource: "https://agenticweb.wiki/terms/streamable-http/"
tags: ["glossary", "act"]
status: stable
generated: { by: agenticweb-builder/1.0, at: 2026-10-23T00:00:00Z }
verified: { by: process:agenticweb-engine, at: 2026-10-23T00:00:00Z }
stale_after: 2026-11-22T00:00:00Z
sources:
  - id: ref-1
    resource: "https://modelcontextprotocol.io/specification/2026-07-28/index"
    last_modified: 2026-07-28T00:00:00Z
  - id: ref-2
    resource: "https://blog.modelcontextprotocol.io/posts/2026-07-28/"
    last_modified: 2026-07-28T00:00:00Z
---

# Streamable HTTP

**Streamable HTTP** is the primary remote transport for the **Model Context Protocol (MCP)**, replacing the early dual-endpoint `HTTP+SSE` transport from the 2024-11-05 specification. Under Streamable HTTP, an MCP server exposes a single HTTP endpoint (commonly `/mcp`) that accepts JSON-RPC 2.0 `POST` requests and can respond either with a single `application/json` body or an upgraded `text/event-stream` (SSE) stream when streaming notifications or progress. As of the **2026-07-28** MCP release, Streamable HTTP operates statelessly by default using `MCP-Protocol-Version`, `Mcp-Method`, and `Mcp-Name` headers without requiring a sticky session handshake. Used by: mcp.

# Knowledge Graph

* **Related standards**: [Model Context Protocol](/okf/protocols/mcp.md)

[^ref-1]: https://modelcontextprotocol.io/specification/2026-07-28/index (https://modelcontextprotocol.io/specification/2026-07-28/index)
[^ref-2]: https://blog.modelcontextprotocol.io/posts/2026-07-28/ (https://blog.modelcontextprotocol.io/posts/2026-07-28/)