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 (Model Context Protocol) was everywhere at Google I/O 2026, not as a novelty or an experiment, but as the assumed plumbing underneath every major agent announcement. The protocol debate is effectively over.

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 their walls, they'll use the open protocol. Cursor, Copilot, Windsurf, Mistral, and Grok all support MCP already. When the company that runs Search, Gmail, Android, and Chrome commits to MCP as the integration layer for its flagship product, the protocol question is settled. A year ago, MCP was a specification from Anthropic. Today it's the default connection layer for Google's most visible consumer AI offering.

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, MCP servers, and server-side tools. The enterprise pitch is operational abstraction: you define the agent, Google runs the runtime. Managed Agents are powered by the Antigravity agent and built on Gemini 3.5 Flash. Developers can define custom agents through versionable markdown files like AGENTS.md and SKILL.md rather than building complex orchestration layers from scratch. Full integration with A2A (Google's Agent-to-Agent protocol) and Agent Platform governance and security is coming soon, but MCP servers are available day one.

WebMCP: The Browser Layer Nobody Saw Coming

The most underreported announcement at I/O 2026 was WebMCP — 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. 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 failure modes. WebMCP lets developers annotate their JavaScript functions and HTML forms so browser-based AI agents can call them directly as structured tools with the same reliability you'd expect from a typed API. 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 — but six major consumer platforms publicly committed to implement it before it's finalized.

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 in GA. The MCP server client is also accessible directly from the Google Security Operations chat interface in preview. The server connects with AI applications including Gemini CLI, ChatGPT, Claude, and custom applications you're developing. This matters because security operations is one of those domains where agent reliability directly affects risk — a bad tool call can mean a missed threat or a false positive that wastes analyst time. Shipping a managed, remote MCP server here rather than asking security teams to run their own is a meaningful architectural choice with real operational implications.

Genkit 2.0 Bundles Native MCP 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 (generally available) 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. This removes friction at exactly the wrong moment — when you're trying to get something into users' hands instead of tinkering with infrastructure configuration.

A2A Hits 150 Organizations in Production

Google's Agent-to-Agent protocol also had a significant update: 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 matters: 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 layers of the same stack — not competitors.

Key Takeaways

  • Gemini Spark uses MCP for third-party tool integration, signaling Google's commitment to open protocol standards
  • Managed Agents provision MCP servers by default through a single API call
  • WebMCP extends MCP's logic into the browser with structured tool exposure — Chrome 149 origin trial incoming
  • Google Security Operations ships a remote MCP server in GA for enterprise security automation
  • Genkit 2.0 bundles native MCP integration as a first-class feature in its TypeScript AI framework
  • A2A protocol reaches 150 organizations in production, governed by Linux Foundation's Agentic AI Foundation

The Bottom Line

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 into browsers. Genkit bundles native support in GA. 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.