The announcement and its context

On July 28, 2026, the maintainers of the Model Context Protocol announced the 2026-07-28 specification. MCP is an open protocol for connecting AI applications to data sources and tools. This curated briefing, published on September 20, 2026, comments on that announcement and its implications for integration projects.

The headline change is a stateless transport core: each request now carries the information needed to serve it. According to the announcement, this allows calls to be distributed across instances without relying on a shared session. The application can still keep whatever state its own process requires.

Three changes to watch

The post also describes changes to caching, authorization and how the protocol evolves. These points deserve a place in the technical planning of anyone already running MCP integrations.

  • List responses now include information to guide client-side caching.
  • Authorization is strengthened, including issuer validation and binding credentials to the corresponding issuer.
  • A formal policy sets a minimum of twelve months between deprecation and the possible removal of features.

Rizumu’s take for project decision-makers

Our view is that the opportunity should be assessed in light of your existing operations. A team that maintains many connectors can investigate whether the change eases concrete deployment difficulties. For a small project, the priority may still be validating the usefulness of the exposed tools and the quality of the data they query.

Before migrating, take inventory of the clients, servers and versions in use. Ask your technical lead for a comparison in a test environment: queries, authorized changes, errors and recovery after failures. Record what depends on sessions today and who will be affected if an integration stops working.

An integration decision, with a defined scope

A first trial can use a query tool, with limited data and access. Compare the observed behavior with the version in use and document the adjustments needed. Expanding to write actions should take into account the approval process and how results are checked.

The announcement sets a technical direction; the decision to adopt it depends on compatibility and the benefit demonstrated in your project. Check the specification and the release notes for the SDK you use before planning the change. The sources below point to the original announcement and to the revision discussed here.

Sources and references

The proposed applications and hypothetical examples are Rizumu’s editorial interpretations.

From this read to your business.

Let’s find where this topic meets a challenge in your company.

Talk to Rizumu