0Pricing
MCP Academy · Lesson

The Streamable HTTP Transport

How MCP runs over a single HTTP endpoint.

The Streamable HTTP Transport is a free MCP Academy lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the MCP Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Meet Streamable HTTP

MCP's modern remote transport is called Streamable HTTP. It lets your server live behind one web URL that any client on the internet can reach.

One Endpoint to Rule Them All

Unlike older designs, Streamable HTTP uses a single endpoint, often something like /mcp. Both requests and replies flow through that one path.

POST https://api.example.com/mcp

Clients POST Their Messages

To call a tool, the client sends a normal HTTP POST to the endpoint. The body is the same JSON-RPC message you already learned about. 📨

Two Ways to Answer

The server can reply in two shapes: a plain JSON response for quick calls, or an event stream when it wants to send results bit by bit.

The Accept Header Decides

The client's Accept header signals what it can handle. Listing both JSON and the event-stream type lets the server choose the best reply format.

Accept: application/json, text/event-stream

It Is Still JSON-RPC

The transport changed, but the language did not. Every message over HTTP is the same JSON-RPC request, response, or notification you met earlier.

Turning On HTTP in the SDK

With the Python SDK you flip one switch: run your server with the streamable-http transport instead of stdio. The tools stay exactly the same.

mcp.run(transport="streamable-http")

It Speaks Plain HTTP

Because it is ordinary HTTP, it plays nicely with the whole web stack: load balancers, proxies, and TLS all work without anything special. 🌐

Stateful or Stateless

Streamable HTTP can run stateful, remembering a session, or stateless, treating each call fresh. You choose based on how your server holds context.

It Replaced an Older Transport

An earlier HTTP+SSE design used two separate paths and was clunkier. Streamable HTTP replaced it as the recommended way to serve MCP remotely.

Why It Matters

This single-endpoint design is what makes a remote MCP server practical to deploy and easy for any client to connect to from anywhere.

Quick Check

How does a client send a tool call over Streamable HTTP?

Recap: Streamable HTTP

Streamable HTTP serves MCP over one HTTP endpoint: clients POST JSON-RPC, and the server answers with JSON or a live event stream. Same logic, remote reach. 🚀

Frequently asked questions

Is the “The Streamable HTTP Transport” lesson free?

Yes — the full text of “The Streamable HTTP Transport” is free to read here on the web, and the MCP Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the MCP Academy course, upgrade to CoddyKit PRO.

What will I learn in “The Streamable HTTP Transport”?

How MCP runs over a single HTTP endpoint. You practise MCP Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start MCP Academy?

No prior experience is required. MCP Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “The Streamable HTTP Transport” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this MCP Academy lesson?

Yes. Every MCP Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. Why stdio Isn't Enough
  2. The Streamable HTTP Transport
  3. Streaming Replies with SSE
  4. Sessions & Reconnection
← Back to MCP Academy