🎧 Prefer to listen?

A few weeks ago at Google I/O 2026, between the Gemini 3.5 Flash demo and the smart glasses reveal, someone said the words “WebMCP” on stage. Most people missed it. I didn’t.

WebMCP (Web Model Context Protocol) is a proposed W3C standard, built by Google and Microsoft engineers, that lets websites expose structured “menus” of actions for AI agents. Instead of guessing which button to click, an agent reads the menu, sends the right data, and gets a structured result. It’s currently in Chrome 149 origin trial as of mid-2026.

What problem does WebMCP solve?

When you ask an AI assistant to book a flight or add something to your cart today, it has to figure out what to do by looking at the page — buttons, links, form fields — and guessing. This is screen scraping. It’s slow, it breaks whenever a site redesigns, and it makes mistakes. The kind where you end up booking three hotel rooms instead of one.

I wrote about how AI currently calls tools a few weeks ago. The short version: AI models connect to external services through APIs and structured tool calls. But websites were the missing piece. WebMCP fills that gap by giving every website a machine-readable action menu — not a visual one, but a structured list that says “here’s what you can do, here’s what data to send, and here’s what you’ll get back.”

How is WebMCP different from browser automation?

If you’ve used Gemini in Chrome or any browser automation tool, you know the current experience is hit-or-miss. Sometimes it works. Sometimes it clicks the wrong thing. Sometimes it fills out a form incorrectly and you redo everything manually.

WebMCP replaces that guesswork with certainty. Instead of the AI saying “I think this button does what you want,” the website says “this function does exactly what you want, and here’s how to call it.” The difference is like giving someone directions by saying “look for the big tree and turn left” versus giving them GPS coordinates. One works when conditions are perfect. The other works every time.

What does WebMCP mean for regular users?

Shopping gets smarter. Imagine telling your AI assistant “find me running shoes under $80 in my size and add them to my cart.” With WebMCP, the shopping site’s AI menu includes an “add to cart” function that takes your size, budget, and preferences as inputs. The agent calls it directly. No clicking through filters. No entering your size three different times.

Booking travel gets simpler. Instead of clicking through seven screens to book a flight, your AI agent calls the airline’s “book flight” function with your dates, preferences, and payment info. The whole thing happens in one step.

Filling out forms becomes automatic. Every contact form, application, or signup page that supports WebMCP becomes something your AI can fill out correctly on the first try. No more “please enter your phone number in the format (XXX) XXX-XXXX” errors.

AI search results get better. When AI-powered search engines recommend websites, they’ll prioritize sites with WebMCP support — because those sites let the AI actually complete tasks, not just provide links. If you run a website, this matters for your visibility in AI search results.

What’s the three-protocol stack Google announced?

Google didn’t announce WebMCP in isolation. It’s part of a bigger picture:

  • MCP (Model Context Protocol) handles connections between AI and your tools, databases, and APIs. I covered this in how AI calls other tools.
  • A2A (Agent-to-Agent) lets different AI agents talk to each other and coordinate tasks.
  • WebMCP handles the browser layer — AI agents interacting with websites.

Together, these three protocols answer the question “how does an AI agent actually do things in the real world?” MCP handles the backend. A2A handles agent coordination. WebMCP handles the web.

Should you care about WebMCP right now?

Honestly? Not yet — but soon.

WebMCP is in Chrome 149 origin trial right now. That means developers can start testing it, but it’s not available to regular users yet. The standard is still being finalized through the W3C.

Here’s what I’d watch for:

  • Browser support. Chrome is first. If Microsoft and other browsers adopt it (and the W3C backing suggests they will), this becomes a web standard, not a Chrome feature.
  • Website adoption. The sites that adopt WebMCP early will get priority in AI-powered browsing and search. If you run an online business, this is something to start thinking about.
  • AI assistant support. Once ChatGPT, Gemini, and other AI assistants support WebMCP, the experience of using AI to browse and shop will go from “sometimes works” to “just works.”

What are the open questions around WebMCP?

A few things I’m paying attention to as this moves forward.

Security. If websites can define what AI agents can do, what stops a malicious site from registering fake tools? The security model needs to be airtight before this touches anything involving payments or personal data. That’s a real concern, not a theoretical one.

Cross-browser adoption. Chrome-first is fine for now, but this only becomes a real standard when it works everywhere. The W3C backing is promising, but standards processes are slow. We’re talking years, not months.

The long tail. Big e-commerce sites will adopt this first. But the real shift happens when every small business website, every booking page, every contact form supports WebMCP. That’s years away, but it’s the direction.

If you want to understand more about how AI agents work under the hood, check out my breakdown of AI orchestrators and how AI calls other tools. WebMCP is the next piece of that puzzle.

I test AI tools so you don’t have to. Want to see what else is changing? Check out the tools I actually use every day or start here if you’re new to all this.