The Model Context Protocol (MCP) has released its biggest update yet, a release candidate that removes the transport layer many servers were built around. The new version simplifies the protocol by eliminating the need for custom transport implementations, moving to a simpler HTTP-based model. This change will require existing MCP servers to be rewritten, but promises better interoperability and reduced complexity.
A Major Overhaul
The release candidate, version 2026-07-26, represents a fundamental shift in how MCP works. Previously, servers had to implement their own transport layer, which led to fragmentation and compatibility issues. The new version standardizes on HTTP, making it easier for developers to build and maintain MCP servers.
"This is the biggest change we've made to MCP since its inception," said the MCP team in a blog post. "We've listened to feedback from the community and realized that the transport layer was causing more problems than it solved."
The removal of the transport layer means that existing MCP servers will need to be updated to work with the new protocol. The team has provided migration guides and tools to help developers make the transition.
What Changes
The new version of MCP replaces the custom transport layer with a standard HTTP interface. This means that servers can now be built using any HTTP framework, and clients can communicate with them using standard HTTP requests.
The protocol also introduces a new message format that is simpler and more consistent. Messages are now JSON-based, with a clear structure that makes them easier to parse and generate.
Another key change is the removal of the concept of "resources" and "tools" as separate entities. In the new version, everything is a resource, which can be accessed and manipulated using standard HTTP methods.
Impact on Existing Servers
Developers who have built MCP servers will need to rewrite them to work with the new protocol. The MCP team has provided a migration guide that walks through the changes step by step.
"We understand that this is a significant change, and we apologize for any inconvenience it may cause," the team said. "However, we believe that this change is necessary to ensure the long-term success of MCP."
Stay ahead of the AI curve
The most important updates, news, and content — delivered weekly.
No spam. Unsubscribe anytime.
The team has also released a compatibility layer that allows existing servers to work with the new protocol, but they recommend that developers migrate to the new version as soon as possible.
Community Reaction
The announcement has generated a lot of discussion in the developer community. Some developers have expressed frustration at having to rewrite their servers, while others have welcomed the simplification.
"I've been waiting for this change for a long time," said one developer on the MCP forums. "The transport layer was always a pain point, and I'm glad to see it go."
Others have raised concerns about the migration process. "I have a production server that I've been running for months," said another developer. "I'm not looking forward to having to rewrite it."
The MCP team has acknowledged these concerns and has promised to provide support throughout the migration process.
Looking Ahead
The release candidate is the first step towards a stable release of MCP 2.0. The team plans to gather feedback from the community and make any necessary changes before the final release.
"We're excited about the future of MCP," the team said. "This change opens up new possibilities for the protocol, and we can't wait to see what developers build with it."
The final release is expected later this year.