The plumbing standard behind AI agents just got boring — which is excellent news
The July revision of the Model Context Protocol removes the hardest part of running agent integrations in production. Boring infrastructure is what you want to build on.
What changed
The Model Context Protocol — MCP, the emerging standard for connecting AI agents to business systems, think of it as the USB socket agents plug into — published a major revision on 28 July. The headline change: it no longer requires a running "session" between agent and tool. Each request now stands alone, which means, in the spec's own words, any request "can land on any server instance behind a plain round-robin load balancer" — the same ordinary infrastructure that already runs your website.
The revision also lets a tool pause mid-task and ask the user a question, and tightens how integrations prove who they are.
Why it matters to you
Session-based protocols are the expensive kind to run reliably — they need sticky connections and careful failure handling, which in practice means specialist hosting and specialist people. Stateless request/response is the cheap, well-understood kind. Every IT team on earth already knows how to run it.
For a business buying agent integrations rather than building them, that shifts two things: hosting an integration gets cheaper and more reliable, and you become less dependent on any one vendor's special infrastructure. A standard connector written once works across agents and across the AI models you might switch between later.
What we'd do about it
If a supplier is quoting you for agent integrations, ask whether they're building on MCP. There can be good reasons not to — but "no" now deserves a follow-up question, because a proprietary connector is a dependency and a standard one is an asset. This is also quietly the answer to "what if we pick the wrong AI company?" — standardised plumbing means the model behind your agents becomes swappable rather than structural.
What to watch
Older MCP integrations built on the session-based transport are now on a deprecation clock — the spec gives at least twelve months. If you had connectors built in 2025, a small upgrade conversation with whoever built them belongs on next quarter's list, not next year's.
Sources
Every claim in this article links to a primary source. The agent collects them; the editor verifies each one before publication.
- The 2026-07-28 Specification — Model Context Protocol (official blog) , 2026-07-28
How this was made
Drafted by our research agent from the sources above, then edited, fact-checked and approved by a human before publishing. We publish this note on every article because we think you should know.
More insights
AI agents that browse the open web are already hitting closed doors
Sites are starting to block autonomous agents. If your plan depends on an AI acting like a junior on the public internet, treat that as a fragile assumption.
Meta’s new business terms cover your website, not just your posts
From 30 October, Meta’s commercial terms for business accounts reportedly require AI training on linked website content, with no opt-out except leaving the platforms. Treat that as a licensing and data-protection review, not a footnote.
Square puts voice ordering on a kiosk
Block’s payments firm is selling a 21.5-inch ordering kiosk that talks back. For a shop that already has a counter, that is a staffing question, not a gadget story.