Since our last November release MCP continued to turn astatine an astonishing rate. Across our Tier 1 SDKs, we’re seeing adjacent to half-a-billion downloads a month, pinch some TypeScript and Python SDKs crossing the 1 cardinal full downloads threshold. In conscionable a fewer months, the protocol continued to turn arsenic the information and interactivity substrate for agentic workflows.
Today, we’re officially pushing the merchandise fastener connected the adjacent type of the MCP specification, 2026-07-28, on pinch the SDKs that will let you to commencement building clients and servers correct away.
The item of this merchandise is simply a stateless protocol halfway - MCP is transforming from a bidirectional stateful protocol into a request/response stateless protocol. It was 1 of the astir highly-requested features from developers who were eager to get amended reliability and scalability for their MCP servers.
A short demo of the stateless protocol halfway successful action.There is, of course, much to what we’re introducing pinch this version:
- Every petition is self-describing, pinch an optional find telephone for clients that want capabilities up front, truthful immoderate petition tin onshore connected immoderate lawsuit down a plain round-robin load balancer.
- Method and instrumentality names recreation successful the Mcp-Method and Mcp-Name HTTP headers, truthful gateways tin way and authorize connected headers directly.
- Server-to-client requests for things for illustration sampling and elicitation are being redesigned to usage Multi Round-Trip Requests (MRTR), removing the request for perpetually unfastened bidirectional streams.
- List responses transportation cache hints and a deterministic order, truthful clients tin cache instrumentality catalogs and support upstream punctual caches unchangeable crossed reconnects.
- Formally locking successful connected a due extensions framework, pinch Tasks joining different extensions, specified arsenic MCP Apps and Enterprise Managed Authorization (EMA).
- A group of authorization hardening changes including RFC 9207 issuer validation and a general displacement distant from Dynamic Client Registration (DCR) toward customer metadata documents (CIMD).
- A general deprecation argumentation pinch a twelve-month minimum model truthful you tin scheme upgrades alternatively of reacting to them.
The TypeScript, Python, Go, and C# SDKs are updated to match, pinch elaborate migration notes for the breaking bits - and you tin get started pinch the caller spec correct away.
What changed
No handshake aliases sessions
With the caller spec version, we’ve officially retired the initialize/initialized speech on pinch the Mcp-Session-Id header (refer to SEP-2575, SEP-2567). Each petition now travels connected its own, carrying its protocol version, customer identity, and customer capabilities successful _meta. If a customer wants to study a server’s capabilities earlier doing thing else, there’s a caller server/discover Remote Procedure Call (RPC) for that; however, it is not required. Any petition tin now onshore connected immoderate server lawsuit down a plain round-robin load balancer without needing shared storage.
Dropping the protocol-level convention doesn’t unit your exertion to beryllium stateless. If your server needs to transportation authorities crossed calls, mint an definitive grip from a instrumentality and person the exemplary walk it backmost arsenic an argument. We recovered this useful amended than convention authorities hidden successful the carrier - the exemplary tin spot the grip and thread it betwixt tools.
Multi Round-Trip Requests (MRTR)
MRTR replaces the server-initiated elicitation/create, sampling/createMessage, and roots/list requests that antecedently required a held-open stream.
Sometimes a instrumentality needs thing from the personification mid-call, specified arsenic a confirmation aliases a missing parameter. MRTR (SEP-2322) enables this script complete a stateless protocol: the server returns resultType: "input_required" on pinch the requests it needs answered, and the customer retries the original telephone pinch the answers attached successful inputResponses.
Streamable HTTP requests now must see Mcp-Method and Mcp-Name (SEP-2243). Your gateway, complaint limiter, aliases WAF tin way and metre connected those headers alternatively of parsing JSON bodies.
List results are cacheable
Responses from tools/list, prompts/list, resources/list, and resources/read now transportation ttlMs and cacheScope (SEP-2549). This allows clients to find the champion caching strategy for responses and trim unnecessary re-fetching.
Authorization
From our discussions pinch implementers for the past year, authorization is wherever implementers walk astir of their integration time. With this spec revision, we continued evolving the MCP auth and information posture.
- Authorization servers should return the iss parameter per RFC 9207, and clients must validate it earlier redeeming a codification (SEP-2468). This closes an authorization-server mix-up hole.
- Clients group application_type during Dynamic Client Registration (DCR) truthful authorization servers extremity rejecting localhost redirects for desktop and CLI apps (SEP-837). If you’ve ever wondered why your CLI client’s OAuth travel sewage a redirect_uri error, this is apt why. And while we’re moving to Client ID Metadata Documents (CIMD) arsenic the standard, this is simply a hardening measurement making the protocol comply pinch OAuth spec requirements.
- Client credentials are bound to the issuer that minted them. No reuse crossed authorization servers (SEP-2352).
- Dynamic Client Registration itself is now formally deprecated successful favour of CIMD. DCR continues to activity for backward compatibility, but will beryllium removed successful a early type of the MCP spec.
Tasks
Tasks move retired of the experimental halfway and into the io.modelcontextprotocol/tasks extension, pinch a poll-based tasks/get and a caller tasks/update (SEP-2663). Change notifications move from the aged HTTP GET endpoint to a azygous subscriptions/listen watercourse that clients opt into per notification type.
Deprecations
Roots, Sampling, and Logging are deprecated (SEP-2577). They still work, and they’ll support moving for astatine slightest 12 months. New implementations shouldn’t adopt them. The bequest HTTP+SSE carrier is besides considered to beryllium officially deprecated, pinch a year-long offramp.
SDKs
All 4 Tier 1 SDKs speak 2026-07-28 arsenic of today:
- TypeScript
- Python
- Go
- C#
Beyond the Tier 1 set, the Rust SDK supports the caller spec successful beta.
The SDKs instrumentality APIs that let you to build some servers and clients pinch the caller spec version. As we mentioned successful the SDK beta blog post, location will beryllium immoderate migration cost, particularly for developers that did dangle connected convention identifiers; however, we incorporated early testing feedback that makes this process overmuch easier.
Ecosystem support
As pinch immoderate ample release, the activity that we’re doing pinch MCP would not beryllium imaginable without contributions from folks crossed the ecosystem. We’re besides particularly grateful to a number of contributors and partners who helped america trial and validate the spec earlier it became mostly available.
The 2026-07-28 Model Context Protocol merchandise represents a monolithic leap guardant successful endeavor AI scalability. By evolving into a stateless architecture, this specification removes the clash of deploying agentic workflows astatine scale. At Google Cloud, we are excited to leverage these powerful caller capabilities crossed our ecosystem of developer tools. This merchandise provides the robust, secure, and extensible instauration that our customers (and our ain teams) request to build the adjacent procreation of AI applications, and we are proud to proceed shaping the early of this unfastened modular together.Anna Berenberg Engineering Fellow
Anthropic pairs frontier models pinch a developer acquisition that keeps raising the bar. The stateless halfway successful the unfastened MCP 2026-07-28 spec reduces the complexity we manage, truthful we tin vessel much features to our customers, faster and astatine scale.Andrew Goodman VP of AIGetting started
We’re excited to person developers build connected the caller spec. To get started, mention to the pursuing resources:
- Specification
- Full changelog
- Documentation and guides
Thank you
This merchandise would not beryllium imaginable without a monolithic organization of contributors and manufacture partners. We’d for illustration to admit the dozens of cardinal contributors crossed specification, documentation, SDKs, moving and liking groups, arsenic good arsenic hundreds of independent worldwide communities who rallied support and excitement for MCP. We’re looking guardant to continuing evolving the protocol arsenic it grows!
English (US) ·
Indonesian (ID) ·