There's an uncomfortable fact under all the WebMCP excitement, and the skeptics are right to keep raising it:
As of June 2026, none of the mainstream AI agents actually call navigator.modelContext on your site. Not ChatGPT Agent, not Claude, not Gemini, not Perplexity. They all still read your page by DOM-scraping or by taking screenshots and clicking pixels. Patrick Brosset's updates and studiomeyer's "Reality Check" both lay this out plainly, and it's worth repeating because the hype usually skips it: WebMCP is a W3C Community Group draft, not a standard, shipping behind a flag in Chrome and a Chrome 149 origin trial — and the agents that would consume it haven't wired it up.
So why would you add WebMCP tools to your site right now?
I think there's an honest answer, and it isn't "because it's the future, trust me." Let me make the actual case — including the part most "install it now" posts skip, which is what to do so the install doesn't quietly rot.
The cost side is genuinely near-zero
