WebMCP Origin Trial Launches in Chrome 149 on June 2. Websites Become AI Agent Tools, 8-12x Faster Than Vision Scraping.

Every browser agent you've ever used works the same way. Screenshot the page, parse the pixels, figure out what to click, click it, screenshot again. It's slow, it's brittle, and it breaks every time a site changes its layout. That entire paradigm dies on June 2.

Google's Chrome team is shipping WebMCP as a public origin trial in Chrome 149. The spec lets websites declare JavaScript functions and HTML forms as structured tools that AI agents can invoke directly. No screenshots. No DOM parsing. No guessing which button is "Submit." An agent calls a function, gets a typed response, moves on.

Early benchmarks show 8-12x faster end-to-end task completion on WebMCP-enabled sites versus vision-based agents. I expected improvement, but an order of magnitude caught me off guard.

Two things make this feel real rather than experimental. First, Microsoft co-authored the spec and shipped Edge 147 support back in March. This isn't a single-vendor play. Second, there are two implementation paths: an imperative JavaScript API for custom tool definitions, and a declarative API that adds annotations to standard HTML forms. The declarative path means existing forms can become agent-callable with minimal code changes.

For builders, the action items are concrete. If you run a web app, start adding WebMCP tool declarations before June 2. The imperative API lets you define tools with standard JavaScript, complete with input/output schemas and side-effect descriptions. If you're building browser agents, start testing against WebMCP-enabled sites now instead of investing more in vision-based approaches that are about to become legacy.

The catch: Firefox and Safari have made no commitments. So we're looking at a Chrome/Edge-only world initially. That's roughly 75% of browser traffic, which is enough to build on but not enough to drop fallback scraping entirely. I'd build WebMCP-first with a vision fallback for the near term.

This connects directly to the Agent Infrastructure Wars happening simultaneously. Google's Antigravity SDK, CopilotKit's AG-UI protocol, and Camunda's ProcessOS all shipped in the same two-week window. The pattern is clear: agent interoperability, not model capability, is where the competition has moved. WebMCP is the browser layer of that stack.