Google I/O 2026: MCP Is Now Infrastructure
Google I/O used to be about new models. This year it was about what those models do - and how they connect to everything else. MCP was everywhere.
Not as a novelty. Not as an experiment. As the assumed plumbing.
Here's what actually shipped.
Gemini Spark Will Run on MCP for Third-Party Tools
The headline agent at I/O 2026 was Gemini Spark - a 24/7 AI agent that runs on cloud VMs, works while your devices are off, and handles long-running tasks across Gmail, Docs, and Calendar. Spark integrates with Google Workspace apps first, then expands to third-party tools via MCP over the summer.
That's the part worth sitting with. Google built its flagship consumer agent and then said: for everything outside our walls, we'll use the open protocol. A year ago, MCP was a specification from Anthropic. Today, Google built its flagship consumer AI agent on it. Cursor, Copilot, Windsurf, Mistral, Grok - they all support it too.
When the company that runs Search, Gmail, Android, and Chrome commits to MCP as the integration layer for its flagship product, the protocol debate is effectively over.
Managed Agents Get MCP Servers by Default
Google also launched Managed Agents through the Gemini API - a setup where a single API call provisions a remote Linux environment with its own isolated sandbox. Each agent gets its own ephemeral sandbox provisioned with skills, Model Context Protocol (MCP) servers, and server-side tools. Full integration with A2A and Agent Platform governance and security are coming soon.
Managed Agents are powered by the Antigravity agent and built on Gemini 3.5 Flash. Developers can define custom agents through versionable markdown files such as AGENTS.md and SKILL.md, rather than building complex orchestration layers from scratch.
This is Google offering hosted execution, sandboxing, state handling, and MCP tool access as a bundled service. The enterprise pitch is operational abstraction - you define the agent, Google runs the runtime.
WebMCP: MCP Gets a Browser Layer
The most underreported announcement at I/O 2026 was WebMCP. WebMCP is a proposed open web standard that allows developers to expose structured tools, like JavaScript functions and HTML forms, so browser-based AI agents can execute complex tasks with greater speed, reliability, and precision. The experimental WebMCP origin trial starts in Chrome 149, with support for Gemini in Chrome coming soon.
The problem it solves is real. Browser agents today navigate by reading rendered HTML and guessing where to click. A dynamically injected form field, a JavaScript-rendered dropdown, a modal that loads on interaction - these are routine failures. WebMCP lets developers annotate their JavaScript functions and HTML forms so that browser-based AI agents can call them directly as structured tools - with the same reliability you'd expect from a typed API, not from a model guessing where to click.
The protocol composes cleanly with the rest of the stack: MCP handles agent-to-infrastructure connections (databases, APIs, file systems), A2A handles agent-to-agent coordination across vendors, and WebMCP handles agent-to-website interaction in the browser. Three protocols, three layers.
WebMCP currently lives in the W3C Web Machine Learning Community Group - an incubation space, not the full standards process. The path from origin trial to official standard is long. But six major consumer platforms publicly committed to implement it before it's finalized. That's a credible signal.
Google Security Operations Ships a Remote MCP Server
On the enterprise security side, Google shipped a remote MCP server for Google Security Operations - and made it generally available. You can build your own security agents with remote Google Cloud MCP server support for Google Security Operations, now generally available. You can also access the MCP server client directly from the Google Security Operations chat interface, available in preview.
The Google Security Operations remote MCP server is enabled when you enable the Google Security Operations API. It connects with AI applications including Gemini CLI, ChatGPT, Claude, and custom applications you're developing.
This matters because security operations is one of the domains where agent reliability directly affects risk. Shipping a managed, remote MCP server here - rather than asking security teams to run their own - is a meaningful architectural choice.
Genkit 2.0 Adds Native MCP Server Integration
For developers building agent applications in TypeScript, Genkit 2.0 GA ships as a TypeScript AI framework with native MCP server integration, streaming, Cloud Trace observability, and one-click Cloud Run deployment.
Native MCP integration in a GA framework means developers no longer need to wire MCP separately - it's in the baseline toolchain. Combined with Cloud Run deployment, the path from "I have an MCP server" to "it's running in production" is now shorter than it's ever been.
A2A Hits 150 Organizations in Production - and It Complements MCP, Not Replaces It
Google's Agent2Agent protocol also had a significant update at I/O 2026. A2A has reached 150 organisations in production - not pilot - routing real tasks between agents built on different platforms. The protocol is now governed by the Linux Foundation's Agentic AI Foundation and has reached version 1.2, with signed agent cards using cryptographic signatures for domain verification. Microsoft, AWS, Salesforce, SAP, and ServiceNow are running A2A in production environments.
The distinction from MCP is worth being clear about. MCP handles how an agent connects to tools and data sources. A2A handles how agents communicate with each other across organisational and platform boundaries. They're complementary. The full interoperability stack for multi-agent systems uses both.
What This Actually Means
Google I/O 2026 didn't introduce MCP to the world. It normalized it.
Managed Agents provision MCP servers by default. Gemini Spark uses MCP for third-party tools. Security Operations ships a remote MCP server. WebMCP extends the protocol's logic into the browser. Genkit 2.0 bundles native MCP integration in a GA framework.
None of these are experiments. They're production decisions made by a company that controls a significant portion of the developer toolchain.
If you're building agents, or building tools that agents should be able to call, MCP is the interface layer. That was already true six months ago. Google just made it harder to ignore.
For a fuller breakdown of Google I/O 2026's agent announcements, see the Gentoro analysis.
Top comments (0)