WebMCP lands in Chrome Canary: websites become callable tools, and your MCP server may be optional

The Chrome team shipped WebMCP this week as an early preview in Chrome 146 Canary (behind the "WebMCP for testing" flag at chrome://flags). Co-developed by Google and Microsoft engineers and incubated in the W3C's Web Machine Learning community group, it's a proposed standard that lets any website expose structured, callable tools to AI agents through a new browser API: navigator.modelContext.

Why this matters to you as a builder: today's browser agents interact with your site by screenshotting it or parsing raw DOM — slow, fragile, and token-expensive. WebMCP inverts that. Your site declares the actions it supports, and the agent calls them as functions. There are two surfaces: a Declarative API that makes existing well-structured HTML forms agent-callable by adding tool names and descriptions to the markup, and an Imperative API (registerTool()) where you define tool schemas — conceptually the same shape as OpenAI/Anthropic tool definitions — that run entirely client-side. A single searchProducts(query, filters) call replaces dozens of click-scroll-screenshot rounds.

Two design points worth noting. First, this is not a replacement for MCP — it's client-side and form-factor-different from Anthropic's JSON-RPC server protocol; the two are complementary (back-end MCP server for service-to-service, WebMCP for in-browser sessions where the user is present). Second, the spec explicitly treats headless autonomy as a non-goal — it's built around human-in-the-loop, cooperative browsing.

Practical move: if you own a consumer-facing web app, audit which of your flows are clean HTML forms — that's reportedly "80% of the way there" for the declarative path. DataCamp already has a hands-on tutorial if you want to try it in Canary this week.

Sources: VentureBeat, WebMCP spec site, DataCamp tutorial