MCP 2026-07-28 introduces a stateless core and formal extensions framework
The new specification changes how AI applications communicate with tool servers. Each request carries its protocol context, making client–server compatibility and complete user journeys central to implementation testing.
The maintainers of Model Context Protocol released MCP 2026-07-28 on July 28, 2026. Its central change is a stateless core: each request carries the information needed for the server to process it independently.
The release matters to teams connecting AI applications with tools and data. It changes the communication model, making the protocol versions supported by both client and server important implementation details.
What an independent request means
The versioned specification says a server must not infer a new request’s context from earlier requests. Information such as protocol version and client capabilities accompanies each request.
An application can still manage work across multiple steps through an explicit identifier. In an illustrative workflow, a tool creates a draft and returns its identifier. The next request includes that identifier to continue working on the same draft.
This makes the intended object visible at each step. Developers can examine its identifier together with the operation’s result when reviewing the task’s execution.
A useful exercise could include several independent drafts or objects. The team can then check that each request reaches the intended object and that results from separate tasks remain correctly associated.
Completed work or additional input
The specification distinguishes complete and input_required results. The latter indicates that an operation needs additional input before it can finish.
If a tool needs a user’s choice, the application can be evaluated on how it presents that step. Useful cases include answering, leaving the question unanswered and encountering an error during the request.
Another test can examine what users see when returning to the task. Is its status clear? Can they identify the object on which work will continue? These are design examples; assessing a particular application requires observing its actual behavior.
Extensions and product support
The MCP launch announcement also introduces a formal extensions framework and authorization updates. Anthropic announced a rollout of support across Claude products, describing adoption as a process being brought to its applications.
For an integration team, a practical starting point is to identify the client and server versions, then run a short task from beginning to result. The request, object identifier and outcome can be examined together, including a case that requires additional interaction.
Recording the expected behavior beforehand makes it easier to compare the actual result and locate a discrepancy.
The significance of MCP 2026-07-28 is its more explicit model for tool communication at the request level. Its implementation value becomes visible when both sides work together and the complete user journey can be followed and understood.
Sources
Founder and editor-in-chief of Kurd Developers. Phone and tech news on YouTube, Instagram and TikTok.
More stories
Apple Intelligence Is Coming to China With iOS 27.3, Backed by Alibaba
After more than two years of waiting, Apple says Apple Intelligence will reach iPhone users in China in December, with Alibaba's Qwen model powering parts of Siri.
One text can break your phone: Android's 'SMS of Death' explained
A flaw in Android 12 and later lets a specially crafted SMS drop calls and even make a phone unusable. The fix is in October's security patch.
GTA VI lands November 19: prices, editions and what to know
Rockstar has locked the date: Thursday, November 19 on PS5 and Xbox Series X|S. Standard costs $79.99 and Ultimate $99.99.
Apple's first touchscreen MacBook Pro brings OLED and Dynamic Island
The new PROLED XDR display responds to touch, the notch is gone and Dynamic Island takes its place. Prices start at $2,899.