Shrutam CCA-F Crash › Domain 2 › d2-l06-stdio-vs-sse English Hinglish →

MCP Transport — stdio vs SSE vs HTTP

Domain 2 · 20% ~12 min English narration

Scenario anchor

Aaranya IT ke ek BFSI client ke liye aap ek multi-agent MCP pipeline design kar rahe hain — ASX-India ke real-time trade reconciliation workflow mein. Aapke senior architect ne poocha: "stdio use karo ya SSE?" — aur galat answer dene se ya toh latency spike aayega, ya production container crash karega. Is lesson ke baad aap confidently justify kar sakte hain ki kaunsa MCP transport kab aur kyun choose karna hai.

Key Takeaways

stdio transport sirf single-process, same-host deployments ke liye valid hai — jaise CLI tools ya local agent loops; kisi bhi networked ya containerized architecture mein stdio architectural dead-end hai.
SSE (Server-Sent Events) server-to-client streaming ke liye optimized hai lekin stateful persistent connection require karta hai — sticky sessions ya connection-aware load balancing ke bina horizontal scaling broken ho jaata hai.
Streamable HTTP transport (MCP 2025-03 spec) stateless request-response semantics deta hai with optional streaming upgrade, making it the correct default for enterprise deployments behind API gateways, reverse proxies, aur service meshes.
Memory anchor: jaise service-mesh sidecar protocol negotiation mein aap transport capability ko deployment topology se match karte hain — MCP transport selection bhi wohi principle follow karta hai: process boundary aur network topology pehle, convenience baad mein.

← Previous lesson Same lesson in Hinglish Next lesson → Back to overview