Skip to content

Streamable HTTP and stdio: the two MCP transports

Glossary entry. Checked on 19 November 2026 against MCP spec 2026-07-28.

Streamable HTTP and stdio, in plain words

MCP has two standard transports. stdio connects an app to a server it starts on the same computer, through standard input and output. Streamable HTTP connects an app to a server over the network with HTTP POST, optionally streaming responses, and supports normal web authentication.

Which to use

  • stdio for local servers: no network, one app per server, and the security guidance recommends it for local servers because only the app that started the server can talk to it.
  • Streamable HTTP for remote servers: one server for many users, with bearer tokens, API keys or OAuth.

What about SSE?

The older HTTP+SSE transport is deprecated in the 2026-07-28 spec, with a year-long off-ramp. Some apps still accept it; Antigravity, for example, only takes Streamable HTTP for remote servers.

Share this definition

Sources

Official documentation, checked on 19 November 2026. Products change: if a step differs, the source has the current version.