Gemini in Chrome is about to call WebMCP. The "no agent uses it yet" excuse just got an expiry date.

For most of 2026 the honest objection to WebMCP went like this: "Cool API. But no mainstream agent actually calls navigator.modelContext, so why ship it?"

I've made that argument myself in writing — it was true, and it was the right question to ask before spending a sprint on it.

Google just changed the answer. In its Google I/O 2026 round-up, the Chrome team wrote, plainly:

"Gemini in Chrome will soon support WebMCP APIs."

And as one developer who shipped WebMCP on their own site put it: "The sole agent consuming those tools today is Gemini in Chrome." So the picture for mid-2026 is: one named, mainstream, hundreds-of-millions-of-installs agent is the first real consumer — and it's coming from inside the browser most of your users already run.