Clip / Other

MCP moves to a stateless request-response model

From Did Anthropic finally fix MCP? · ≈3:13

“The fifth spec release of the model context protocol MCP 202060728 is live today.”

“MCP has moved from a birectional stateful protocol to a request response model.”

“Servers can now deploy on serverless and edge infrastructure.”

“This simplifies the experience of building MCP servers for Claude and scaling their usage as they grow in adoption.”

What’s in it

Breaks down the new MCP spec's shift to a stateless request-response core
Explains why servers can now run on serverless and edge infrastructure
Covers hardened authorization and newly graduated official extensions

Watch this moment ↗

Clip transcript

worry. The fifth spec release of the model context protocol MCP 202060728 is live today. The latest spec moves MCP to a stateless core while hardening authorization and graduating official extensions. Support is being rolled out across clawed products. This is the big part here that MCP has moved to a stateless core. Very very very exciting. What do we mean by this stateless core? Well, according to Enthropic, MCP has moved from a birectional stateful protocol to a request response model. Huh, almost like the exact thing I've been saying it should do for a long time now. Servers can now deploy on serverless and edge infrastructure. This simplifies the experience of building MCP servers for Claude and scaling their usage as they grow in adoption. Yep,

Intel