Netlify says the new MCP spec makes servers stateless and easier to ship
thisiskp_ · x · 2026-07-29
Netlify says the new MCP 2026-07-28 spec makes MCP servers stateless by default, turning them into ordinary HTTP workloads.
The company argues this removes much of the operational pain of building MCP services:
- no sticky sessions
- no session store
- no shared state across instances
- no need to keep long-lived connections warm
Netlify’s key claim is that teams who would never build an always-on stateful service can now ship an MCP server in an afternoon, and it scales like any request-driven workload once users arrive. The company also says this strengthens Agent Experience (AX) because agents need services they can discover, call reliably, and recover from when something fails.
Related event: MCP's Epic Update: Shifts to Stateless Core(9 posts)→
More from coding & agent
- Hermes Agent Adds Native ACP Support for Seamless Editor Integration — max_paperclips · 2026-07-29
- Hidden Trick: Manually Invoke Older Opus Models in Claude Code — voooooogel · 2026-07-29
- Meme shows why telling an agent to “implement the fix cleanly” changes everything — giffmana · 2026-07-29
- MPP launches a new site for machine-to-machine payments — jeff_weinstein · 2026-07-29
- Anaconda says coding harnesses help enterprises switch between open and closed models — anacondainc · 2026-07-29
- An AI agent tries to sell a driveway repaving with a slide deck — Flomerboy · 2026-07-29