When @jspahrsummers (Anthropic) proposed replacing the original HTTP+SSE transport with "Streamable HTTP" in [specification PR #206][pr-206], the PR body included an explicit "Why not WebSocket?" section. The core team's stated reasons were:
- RPC overhead -- Using MCP in a stateless "RPC-like" way (e.g., a server