For years AI agents operated on the web like blind passengers: taking screenshots, guessing where buttons were, and navigating through interfaces built for humans rather than for them. WebMCP changes the approach at the root. The emerging W3C standard — co-developed by Google and Microsoft and currently in an origin trial in Chrome — gives websites a structured way to expose their own functionality as callable tools. Instead of reverse-engineering the page, the agent simply asks what the site can do. The site answers.
How it works
The core of WebMCP is the navigator.modelContext API. As a website developer you register one or more tools: JSON Schema descriptions of what your app can do — search, add to cart, reserve a date — including the parameters each action requires. The browser stores those registrations and makes them available to AI agents running inside Chrome. When an agent wants to take action on your site, it picks the right tool and calls it with the correct parameters, exactly the way a developer calls an API. No screenshot, no click simulation, no guessing.
State of play in July 2026
WebMCP is currently running in a public origin trial from Chrome 149 through Chrome 156, with a spec draft updated as recently as last week. The Lighthouse suite already has an audit category ready for it. Real-world deployment on live websites is still minimal, though: most mainstream AI agents that consumers use daily do not speak WebMCP yet. The standard has everything right now except users. That makes this the ideal moment to learn it — the adoption curve follows browser support, not the other way round.
Our take
WebMCP inverts the relationship between website and agent. Today the agent adapts to the site by guessing and clicking. With WebMCP the site presents itself in a structured way — and that is a fundamentally different dynamic. For web apps with actions an agent can usefully call — bookings, searches, forms — this is the standard to track right now. Getting in early costs little: it is extra metadata on top of what you are already building. Waiting means retrofitting structure into a world that will already expect it.
