MCP is dropping sessions, with the final spec due July 28
The lead maintainers of the Model Context Protocol froze the release candidate on May 21 and expect to ship the final spec on July 28, The New Stack reports. Sessions and the startup handshake are being cut from the protocol outright, and three more base capabilities are moving to deprecated status.
Six separate proposals for revising the spec collapse into a single idea: every request has to stand on its own. The protocol version and client capabilities now ride in the _meta field of each call, and server capabilities are fetched with a server/discover method.
The lifecycle policy gives each capability at least 12 months in Deprecated. That window can only be shortened for an active security threat, and never below 90 days.
Beta SDKs are already available for Python, TypeScript, Go, and C#.
Up next
Claude Code keeps your session data locally for 30 days
Claude Code stores session transcripts in plaintext under ~/.claude/projects/, kept 30 days by default so you can resume work. Adjust the window with cleanupPeriodDays. On Free, Pro, and Max, server retention jumps to 5 years if you opt into model training.
Related stories
- MCP goes stateless in its biggest update yet
- Blender addon makes Claude twice as efficient with nodes
- Anthropic hands Agent Skills to the foundation behind MCP
- Claude API sends its traces to your observability tool
- Anthropic’s daily-brief agent treats a failed read as news
- Claude’s SDKs run the click loop, but the browser is yours
Comments
No comments yet. Be the first.
Join the conversation
Sign in to leave a comment. It appears after moderation.