Agent Infrastructure · 4-minute read
AI agents become useful when they can reach tools and data. That makes the connection layer one of the most important—and least visible—parts of the product.
The 28 July 2026 Model Context Protocol revision removes dependence on persistent sessions, adds a governed extension system and strengthens alignment with enterprise authentication. The changes make MCP easier to route through standard infrastructure while improving tracing, caching and migration.
What happened
Earlier MCP connections began with a handshake and relied on a session identifier across later requests. At scale, that could require sticky routing or shared session storage. Under the revised specification, each request declares the protocol version and carries enough information to be handled independently.
The revision also adds structured extensions, clearer HTTP behaviour, stronger OAuth and OpenID Connect alignment, a fuller JSON Schema vocabulary and cleaner separation between transport failures and tool-level outcomes.
Those details sound like plumbing. They determine whether an agent connection works only in a demonstration or survives production traffic, partial failures and security review.
Why it matters now
Agents are moving from single-model conversations toward systems that coordinate search, code, databases, files and business services. Every connection adds capability and risk.
A stateless protocol is easier to place behind ordinary gateways and load balancers. Requests can be routed, retried and observed without recreating hidden session state. That reduces operational complexity while giving security teams clearer places to enforce policy.
What changes
- For developers: MCP services can scale using familiar web patterns.
- For enterprises: authentication, audit and version migration become easier to integrate with existing controls.
- For users: tools from different vendors can participate in a more portable agent ecosystem.
The tension
Standardisation lowers the cost of connecting tools, but easy connection can encourage excessive permission. A protocol can provide secure mechanisms without deciding which data an agent should be allowed to access. Product designers still need least privilege, consent and understandable controls.
The Agentica IX view: The deepest promise of agent standards is not autonomous software for its own sake. It is the ability for individuals to assemble systems around their own intentions instead of reshaping themselves around one application.
What to watch next
Watch adoption across gateways and cloud platforms, how quickly clients migrate and whether interoperable permission standards emerge. The next phase of MCP will be judged less by connector count than by reliability and user control.
Primary reading: AWS: How AgentCore Gateway supports MCP 2026-07-28.