MCP goes stateless: serverless servers, plus MCP Apps and Tasks
Anthropic's biggest MCP rewrite yet: no sessions, mid-operation input, hardened OAuth, and day-one Tier-1 SDKs — with real migration cost for authors.
Copy markdown
Stateless core: MCP servers go serverless
The 2026-07-28 spec kills the initialize/initialized handshake and session IDs — every request now carries its own version, identity, and capabilities. That means MCP servers run behind standard load balancers on serverless or edge infra, with no shared session store to babysit.
MCP Apps: interactive UI inside the chat
Apps is now a formal extension: a tool can render live interactive UI directly in the conversation. You could ship a connector that shows a form or dashboard inline instead of dumping text — no tab-switching for the user.
MCP Tasks: long-running work, first-class
Tasks standardizes long-running operations, so an agent can kick off a build, a deploy, or a data job and track it to completion. Pair it with Apps for a weekend project: an MCP server that runs the job and streams status back into the chat.
Mid-operation input without open streams
Multi Round-Trip Requests let a server pause and ask for a confirmation or a missing param mid-call: it returns resultType 'input_required' and the client retries with the answers. Human-in-the-loop prompts without holding a bidirectional socket open.
Tier-1 SDKs shipped day one
TypeScript, Python, Go, and C# SDKs already support the spec, with Rust in beta. You can build against 2026-07-28 today rather than waiting weeks for tooling to catch up.
The catch: hardened auth and a migration cost
OAuth gains RFC 9207 issuer validation and swaps Dynamic Client Registration for Client ID Metadata Documents — safer, but servers that leaned on session IDs need reworking. It's rolling out across Claude's 950+ connectors, with private-network MCP tunnels in research preview.