Skip to content

Comment on MCP 2026-07-28 Specification: transport going stateless

Comments

We built ours stateless before the spec allowed it. No SSE at all and GET just returns 405, everything is a plain POST about 46 tools.

We were betting clients would cope, and most of them did. When one did not, we had to tell the user their client was the problem, which is never a good look.

The surprise for us was auth getting easier. No session means no confusion about when the key was checked. Anyone can list the tools and actually calling one needs a bearer token or you get a 401.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.