MCP — The Model Context Protocol — an open standard that lets any AI assistant plug into any tool or data source without custom integration code.
Why it matters
If you build or operate MCPThe Model Context Protocol — an open standard that lets any AI assistant plug into any tool or data source without custom integration code.Full definition → servers or clients, this release changes the wire contract: stateless self-describing requests, header-based routing, MRTR instead of long-lived streams for sampling/elicitation, and a shift from Dynamic Client Registration to client metadata documents. The 12-month deprecation window tells you exactly how long your current stateful implementation has.
Key quotes
“Across our Tier 1 SDKs, we’re seeing close to half-a-billion downloads a month, with both TypeScript and Python SDKs crossing the 1 billion total downloads threshold.”
ClaudeDevs
“The highlight of this release is a stateless protocol core - MCP is transforming from a bidirectional stateful protocol into a request/response stateless protocol.”
ClaudeDevs
“With the new spec version, we’ve officially retired the initialize / initialized exchange along with the Mcp-Session-Id header (refer to SEP-2575 , SEP-2567 ). Each request now travels on its own, carrying its protocol version, client identity, and client capabilities in _meta .”
ClaudeDevs
“Dropping the protocol-level session doesn’t force your application to be stateless. If your server needs to carry state across calls, mint an explicit handle from a tool and have the model pass it back as an argument. We found this works better than session state hidden in the transport - the model can see the handle and thread it between tools.”
ClaudeDevs
“Dynamic Client Registration itself is now formally deprecated in favor of CIMD. DCR continues to work for backward compatibility, but will be removed in a future version of the MCP spec.”
