LLM Digest
Subscribe

AI Storyline

2 items · 2 sources · 2 days

View as JSON

Operational story trace

MCP protocol moves to stateless operation

Current stateStateless spec shipped · debatedstatus changed Aug 12

Latest change

InfoQ's Aug 12 follow-up reports developers split over whether shedding session state just turns MCP back into a plain REST API, undercutting the protocol's original pitch as a stateful agent-context layer.

Earlier contextThe story so far

MCP's July 28 spec revision drops the initialize handshake and session header that kept agent-to-server connections stateful, replacing them with required method and tool-name headers so any gateway can route calls without parsing JSON bodies. That change turns MCP traffic into ordinary stateless HTTP requests, the kind load balancers and API gateways already know how to scale.

editor-curated · source-linked

State over time

● spec change · Jul 28 revision, explained Jul 31developer debate · Aug 12 → now ●
  • spec change · Jul 28 revision, explained Jul 31
  • developer debate · Aug 12 → now
SPEC CHANGE · Jul 31
MCP's July 28 spec drops the stateful handshake
1 source · scout · show source ▾
THE DEBATE · Aug 12
Developers ask if stateless MCP is just an API again
InfoQ covers the same spec change and the community split over whether it erases MCP's distinction from REST.
1 source · scout · show source ▾

What to watch — open questions

  • Will major MCP SDKs and gateways make stateless mode the default, or keep the handshake as an option?
  • Does dropping session state break agent memory or context patterns that relied on a persistent MCP session?
  • Does the debate settle on a feature that still distinguishes MCP from plain REST/OpenAPI, or does convergence continue?
How this thread was built
scout surfaced 2editor wrote the arc · 2 beatswatcher 1 status change

Storylines are threaded mechanically from the feed: stories that share a distinctive anchor across multiple days and sources. Each item links to its original source. The evidence trace, current state, and open questions are written by the editor routine and refreshed whenever a new beat lands.