CloudCodeTree LogoCloudCodeTree
AI NewsTutorialsAbout
CloudCodeTree Logo
CloudCodeTree
  • AI News
  • Tutorials
  • About
← Back to AI News
Your MCP Server Has Three Days: What the July 28 Spec Breaks and How to Test Today

Your MCP Server Has Three Days: What the July 28 Spec Breaks and How to Test Today

Chris Harper

2 min read

Jul 25, 2026 · 04:08 UTC

AI
Workflow
MCP
Best Practices

TL;DR: The MCP specification publishes July 28 — protocol goes stateless (no sessions, no init handshake), OAuth 2.1 auth replaces custom flows, and beta SDKs are available to test your server today.

The July 28 MCP spec isn't a minor version bump. Six Specification Enhancement Proposals ship together, restructuring how every MCP server and client communicate. If your server uses session IDs, the initialization round-trip, or sampling, this affects you.

What changes

PatternAfter July 28
Session IDs across callsSessions removed — design for stateless
initialize / initialized handshakeDropped — clients skip this entirely
Sampling (server → host LLM calls)Deprecated — 12-month runway
Roots (filesystem boundary declarations)Deprecated — 12-month runway
Tools-list responsesNow cacheable — add Cache-Control headers

The biggest practical win: MCP servers can now sit behind a round-robin load balancer without sticky sessions. No more "pin this client to this server process" complexity.

Test your server today

The beta SDKs for the new spec are already out:

# Python
pip install mcp==1.11.0b1

# TypeScript / Node
npm install @modelcontextprotocol/sdk@1.11.0-beta.0

Swap in the beta SDK and run your existing test suite. Anything that references session_id, calls initialize, or depends on sampling will surface immediately. Most servers need minor changes — the main surgery is removing initialization handshake code and ensuring handlers don't read from a session context object.

The auth rewrite

The spec now aligns MCP authorization with OAuth 2.1 and OpenID Connect, which makes enterprise integration significantly easier. If your server's current auth was hand-rolled for the draft spec, expect to update it — the new flow follows standard OIDC patterns rather than MCP-specific conventions. The WorkOS guide linked below covers the new auth flow in detail.

Sources: MCP 2026-07-28 Release Candidate · Beta SDKs Available · MCP Auth Changes (WorkOS) · Migration Guide (AAIF)