AI Engineering/Phase 13/Lesson 09

MCP Transports — stdio vs Streamable HTTP vs SSE Migration

stdio works locally and nowhere else. Streamable HTTP (2025-03-26) is the remote standard. The old HTTP+SSE transport is deprecated and being removed in mid-2026. Picking the wrong transport costs a migration; picking the right one buys a remote-hostable MCP server with session continuity and DNS-rebinding protection.

Learn 45 min Python (stdlib, Streamable HTTP endpoint skeleton)

Prerequisites: Phase 13 · 07, 08 (MCP server and client)

#Learning Objectives

Pick between stdio and Streamable HTTP based on deployment shape (local vs remote, single-process vs fleet).
Implement the Streamable HTTP single-endpoint pattern: POST for requests, GET for session stream.
Enforce Origin validation and session-id semantics to defeat DNS-rebinding.
Migrate a legacy HTTP+SSE server to Streamable HTTP before the mid-2026 removal deadlines.

Full Access lesson

Keep going. The rest of this lesson is one step away.

Unlock all 503 lessons, video, code, quizzes and every future update. Pay in your own currency with Paystack.

See plans Sign in

The text and code of this lesson are based on AI Engineering from Scratch by Rohit Ghumare, MIT licensed.