WebMCP lets a website expose its features as structured tools that AI agents call directly, instead of scraping the DOM or reading screenshots. On May 19, 2026, at Google I/O, Chrome announced an origin trial (Chrome 149) that makes it testable on real traffic for the first time. The popular take is that this guarantees your site gets cited and gets referral traffic. The W3C draft does not say that. For sites that earn their living from citations, WebMCP may even sharpen the zero-click problem rather than solve it.
This guide is built from the primary source — the W3C Web Machine Learning Community Group draft — plus the Chrome for Developers origin-trial documentation, not from secondhand explainers. Where the popular framing and the spec disagree, this notes it. Figures and spec details reflect May 2026; WebMCP is a Community Group draft, not a finished standard, so specifics will move.
Why This Guide Exists
Search the web for WebMCP today and you get two kinds of articles: "what is it" explainers and marketing pieces promising it will make your site the one agents pick. Almost none separate what the spec normatively defines from what vendors hope it becomes. A few load-bearing claims circulating — that WebMCP mandates source citation, that it speaks JSON-RPC, that you register "resources" — are not in the current draft. If you plan a content or GEO strategy on those claims, you are planning on something that does not exist yet.
