The Model Context Protocol (MCP) now runs in roughly 78% of enterprise agent stacks, with more than 400 million SDK connections a month. The architecture change of 28 July — a stateless core plus two extensions, Tasks and MCP Apps — and its absorption into the Linux Foundation’s Agentic AI Foundation turned the protocol from one company’s product into a community standard.
From resisted to built in
What is striking is the speed of the turn. In July, Google, Microsoft and Salesforce still formed an explicit hedging alliance; by September Google was using MCP as the bridge into its smart-home platform; in October Google Cloud’s Agent Gateway supported it natively. The direction looks more like absorption than concession.
Neutral protocol, non-neutral gateway
The protocol went to a foundation, but traffic still passes through gateways. Oracle, Google Cloud and Cloudflare built MCP into their clouds in the same week, which shows where control has moved: from the protocol itself to whoever owns the discovery and routing layer in the middle. For users this means an open protocol is not the same thing as a neutral channel.
A security layer growing alongside
Published MCP servers passed 1,200 in mid-October. In Stacklok’s 2026 survey, nearly half of the software companies surveyed already use MCP in production and 19% have deployed it widely. The more connectors there are, the larger the attack surface — products aimed specifically at MCP are appearing, treating these as live, authenticated channels rather than ordinary interfaces.
What it means for enterprises
- When exposing a system’s capabilities outward, wrap it once the MCP way so any number of agents can reuse it — cheaper than writing an interface for every client.
- Treat the MCP gateway as a boundary: who called, what they called and whether they went beyond their rights must all be queryable.
- Do not let agents connect straight to a production database. Put a narrowed permission view in between, so a problem can be cut off in one move.
- When choosing, ask who maintains your connector list — once connectors grow, maintenance costs more than integration.
Want to talk through what you just read?
We work end to end, from product design to launch. Tell us about your scenario and we can start there.
Shenzhen XZS Technology Co., Ltd. · Tel 0755-82494862 · 13760424861