I joined the IAB NZ AI and Search Summit this afternoon, on a panel of local specialists alongside keynotes from speakers at Google, OpenAI, Amazon and others. Each of us on the panel was asked to bring a hot take, and mine came under the umbrella of “how do you influence the influencer, when that influencer is an agent?”
My take was that agentic influence is going to be about utility. The brands that win will be the ones that prioritise the tools agents need to act — and with WebMCP on the horizon, now is the time to start planning.
Here's what you need to know about WebMCP.
Your website already has two audiences. One is human. The other is an AI agent trying to book the flight, complete the checkout, or answer the query on someone else's behalf — and right now, it's doing that by guessing.
Agent browsers today work by screenshotting your page, parsing the DOM, and simulating clicks the way a human would. It's slow, it's brittle, and it breaks the moment your layout changes. WebMCP is Google and Microsoft's answer: let the website tell the agent what it can do, instead of making the agent work it out.
What it actually is
WebMCP is a proposed web standard, incubated through the W3C Web Machine Learning Community Group, that lets a site expose its own functionality as structured, callable tools — the same idea as the Model Context Protocol, but running client-side in the browser tab instead of on a server. The page becomes its own tool registry. BookFlight. searchProducts. Checkout — and that one only appears once there's something in the cart.
There are two ways to build it. A declarative API annotates standard HTML forms directly, for simple, well-defined actions. An imperative API gives you JavaScript for anything more dynamic — state management, multi-step flows, custom validation. Each tool ships with a natural-language description and a JSON Schema for its inputs and outputs, so an agent knows exactly what it's calling and what it'll get back.
For anything that matters — a purchase, a booking, a form submission — the spec keeps a human in the loop. Sites can require a confirmation dialog before a sensitive tool actually fires.
Where it stands right now
Early preview only. It needs Chromium 146.0.7672.0 or higher, and it's sitting behind a flag — chrome://flags/#enable-webmcp-testing — so today that means Canary or Beta, not the browser your customers are running. Microsoft co-authored the spec, which makes Edge support likely, and Mozilla and Apple both have representatives in the W3C working group. None of them have published a timeline. Chrome is the only browser with a working implementation.
Lighthouse has already started paying attention. Version 13.3.0, shipped 7 May 2026, moved an "Agentic Browsing" category into its default config — signals around llms.txt and WebMCP annotations, deliberately not rolled up into a single 0–100 score, because the spec team's own words are that the standards for the agentic web are still emerging and the priority is gathering data over handing out a grade.
Why this matters before it's finished
The pattern is familiar. Structured data and schema.org didn't matter until search engines started reading them, and then every site that hadn't bothered was playing catch-up. The same shift is coming for agents, except the incentive is sharper: an agent that can't parse your checkout doesn't rank you lower, it just doesn't complete the transaction. It goes to the competitor whose site it can actually operate.
You don't need to ship WebMCP tools this week. You do need to know which of your flows — search, booking, checkout, account actions — would be worth exposing first, and you need someone on your team who's actually opened the flag and tried it, rather than reading about it after Edge and Safari have shipped and every competitor already has a head start.
Start with an audit of your own forms. Ask which ones an agent would need to complete on a customer's behalf. That's the list you build from when the flag comes off.
Sources: developer.chrome.com/docs/ai/webmcp; GoogleChrome/lighthouse changelog and release v13.3.0; GoogleChrome/modern-web-guidance.
