MCP Gets Its Biggest Update Yet, and the Goal Is Letting AI Work at Company Scale
A key change to the open standard that helps AI tools talk to outside software removes a bottleneck that made large deployments tricky. Here is what changed and why it matters.
Key points
- The Model Context Protocol (MCP), an open standard for connecting AI systems to external tools, received its largest update since launch in 2024.
- The core change makes MCP "stateless", meaning requests no longer depend on a single dedicated server connection.
- Lead maintainers David Soria Parra and Den Delimarsky, both Anthropic employees, announced the update in a blog post.
- Removing the session dependency directly targets the scaling limits that previously made MCP difficult to deploy across large organisations.
Think of MCP as a universal plug socket for AI. Just as a standard plug lets any appliance draw power from any wall socket, MCP is an open-source standard that lets AI systems connect to outside tools and data sources without each connection needing custom-built wiring. A business might use it to let an AI assistant pull data from a calendar or a customer support system.
The standard launched in late 2024. This week it received its most substantial update so far, as first reported by Ars Technica AI. We've been tracking MCP since 14 July 2026, and our earlier story on Alexa Plus showed how similar plug-in standards are already reshaping consumer products.
What actually changed?
MCP's core is now "stateless". Before this update, every conversation between an AI system and an external tool depended on a continuous session tied to one specific server, a computer that handles requests. Lose that session and the connection breaks. Routing thousands of simultaneous users back to the same server is expensive and complicated.
Stateless design removes that dependency. Each request carries everything it needs, so any available server can handle it. It's the same principle that lets the ordinary web scale to billions of people.
For businesses, the practical effect is real. Deploying AI tools across a company no longer requires building elaborate plumbing to keep sessions alive.
Who made this change?
The update was written by David Soria Parra and Den Delimarsky, the lead maintainers of the MCP specification, who both work at Anthropic. Anthropic originally created MCP before opening it to the wider community.
What does this mean for ordinary users?
Most people will never interact with MCP directly. It sits underneath the products built on top of it, so the benefit arrives quietly. AI assistants built on MCP-connected tools should become more reliable, especially inside larger organisations where many people use the same system at once.
If your employer is piloting an AI assistant that connects to internal data, this update makes it considerably easier for the IT team to run that tool at full company scale without performance headaches.
The real test is whether enterprise developers adopt the new spec quickly. Stateless architecture is a well-understood pattern, so there's no technical mystery here. What matters is how fast the tooling catches up.
Common questions
Do I need to do anything because of this update?
No. MCP is a developer-level standard. If you use a product built on it, any improvements flow through automatically when the developers update their software.
Is MCP only used by Anthropic products?
No. Anthropic created it and still employs the lead maintainers, but the specification is public and increasingly used across the AI industry.
