On 28 July 2026, a new version of the MCP specification was published. The most important change: the protocol no longer maintains sessions, i.e. a persistent connection, and each request carries all the information needed to handle it. This makes servers easier to run in the cloud like any other service, without tying a user to a single machine.
The new version contains changes that are not backward-compatible with the previous one, 2025-11-25. The Roots, Sampling and Logging features have been marked as deprecated; under the project’s rules, they have at least 12 months before they may be removed. The specification also tightens authentication rules, including checking which sign-in system (authorisation server) issued a pass.
For a company with MCP integrations already running, this is a concrete item for the calendar. You need to check with your vendors when they will update their servers and applications. It is also a good moment to sort out authentication and the logging of operations, which were put off during the first rollout.