By Paul GosnellIn this guide
What actually happened on February 10, 2026
On February 10, 2026, the Google Chrome team announced WebMCP - a new browser API that gives websites a standardised way to expose structured tools to AI agents. It shipped as an early preview in Chrome 146 Canary, behind a flag called "WebMCP for testing" at chrome://flags.
The spec was co-authored by engineers from Google and Microsoft, and it formalised what had been a W3C Community Group deliverable since September 2025. VentureBeat described it as "turning every website into a structured tool for AI agents." That framing is accurate.
WebMCP is not the same as Anthropic's Model Context Protocol (MCP). Anthropic's MCP is a backend protocol - it connects AI models to data sources and tools server-side. WebMCP is a client-side browser API that lets your website expose structured actions directly to AI agents running in the user's browser. Different layer, different purpose, complementary rather than competing.
Right now, AI agents can already browse the web - ChatGPT can open pages, Claude can read them, Gemini can use them. But the way they do it is ungainly. Most agents rely on taking screenshots of the page or scraping the raw DOM, then trying to figure out what they're looking at and what they can click. It works, roughly, in the same way a person who can't read the language can still fill in a form if they squint hard enough. It's slow, error-prone, and brittle.
WebMCP gives websites a native way to bypass all of that. Instead of an agent guessing that the blue button probably submits the form, your site can declare: here is a make_reservation tool, it takes a date, a party size, and a contact email, and it returns a confirmation number. The agent calls it directly. No screenshots. No DOM parsing. Structured JSON in, structured JSON out.
The API has two parts:
- Declarative API - You define agent-accessible actions directly in your HTML markup. Simple to add, no JavaScript required. Good for static actions like "contact us" or "get a quote."
- Imperative API - A JavaScript interface for more complex interactions that need dynamic data or conditional logic. Good for booking flows, search, checkout sequences.
Both surfaces communicate with agents via structured JSON, which means agents can reliably parse what your site offers, validate their inputs against your schema, and handle the response programmatically - rather than hoping the confirmation message appears somewhere on the page.
The Chrome Developer Blog post is at developer.chrome.com/blog/webmcp-epp if you want the technical detail.
The four layers of being agent-ready
WebMCP is the most technically significant piece of the puzzle, but it is not the only one. There are four distinct layers to making your site legible and useful to AI agents - and they build on each other.