What is WebMCP and should you care yet?

The 60-second technical version

WebMCP is a browser-side API co-authored by Google's Chrome team and Microsoft's Edge team, incubated through the W3C Web Machine Learning community group. It rides on top of the underlying Model Context Protocol that Anthropic open-sourced in November 2024, but the WebMCP layer itself is the Google + Microsoft work and lives inside the browser tab, not on a backend server.

The page declares what it can do (a Tool Contract). The agent in the same browser tab reads that contract and calls the tools directly. No DOM screen-scraping, no clicking through forms blind. The user asks their agent for something; the agent picks the right tool the site has exposed; the tool runs inside the user's logged-in session and returns structured data.

Why anyone is talking about it

Two reasons. First, agentic AI is the next interface layer. Google AI Mode's agentic features signal that agents acting on websites is the direction of travel. In the UK, AI Mode finds restaurant availability and links you to partners such as OpenTable or TheFork to finish the booking (April 2026). Not every agent has lasted: OpenAI retired its ChatGPT Atlas browser in August 2026. Second, schema and llms.txt only expose content. WebMCP exposes actions. A travel site can let an agent search and book; a SaaS site can let an agent query usage data; an e-commerce site can let an agent add to cart, all without the agent having to figure out where the buttons are.

The two ways to implement it

Top-ranking explainers (Webfuse, Codely, Semrush) all converge on the same split. Two paths, pick by complexity:

• Declarative API (HTML attributes). Add toolname="login" and tooldescription="Log in to your account" to an existing form. The browser registers that form as a callable tool. Lowest-friction path. If your forms are already clean and well-labelled, this is most of the work done.
• Imperative API (JavaScript). Use the new navigator.modelContext.registerTool() browser interface to register tools programmatically. Useful when the action is not a simple form (filtering, multi-step flows, dynamic data). Heavier to wire up.

A concrete example: the login form

Plain HTML form today:

<form action="/login" method="post">
  <input name="email" type="email">
  <input name="password" type="password">
  <button type="submit">Log in</button>
</form>

WebMCP-declared version:

<form action="/login" method="post"
      toolname="login"
      tooldescription="Log in to your account">
  <input name="email" type="email">
  <input name="password" type="password">
  <button type="submit">Log in</button>
</form>

That is it. Two attributes. The agent reads the form's existing input types and required fields as the schema. The tool inherits the user's browser session, so password managers, autofill and cookies all still work the way they do for the human user.

How to try it in Chrome today

Chrome first shipped WebMCP behind a flag in Chrome 146 Canary in February 2026. Chrome's developer docs (last updated 7 October 2026) now give two routes. To test locally, go to chrome://flags/#enable-webmcp-testing, set it to Enabled and relaunch Chrome. To reach real visitors, join the WebMCP origin trial, which runs from Chrome 149. Install the Model Context Tool Inspector extension to see which tools a page has declared. Test against your own site by adding toolname attributes to a form, then asking the in-browser agent to perform the action.

What WebMCP is not

• Not a replacement for schema. Schema describes content. WebMCP describes actions.
• Not a replacement for llms.txt. llms.txt curates content for AI consumption. WebMCP exposes tools for AI use.
• Not the same as Anthropic's MCP. Anthropic's MCP is the underlying protocol and runs server-side (Claude desktop talking to your filesystem, Cursor talking to GitHub). WebMCP is browser-side only, inside the user's tab, on a webpage they have already loaded.
• Not a finished standard. Early preview in Chrome 146 Canary (Feb 2026), then origin trials in Chrome 149 and Edge 150. The specification is still a W3C community group draft, WebKit has said it opposes it and Mozilla's position is neutral.
• Not useful for content-only marketing sites. No action to expose means nothing for WebMCP to do.

Who should consider WebMCP in 2026

• Travel and hospitality (booking, search, reserve)
• E-commerce (search, compare, add-to-cart)
• SaaS with user-facing data (usage queries, account info, integrations)
• News and reference sites with structured data (specific article lookup, fact retrieval)
• Directory and listings sites (filtered search)

Who should skip WebMCP for now

• Consultancy and professional services sites
• Blogs and content marketing sites
• Brochure sites with no interactive layer
• Any site that has not yet shipped basic schema and llms.txt

Primary sources

• Chrome developer blog - WebMCP early preview announcement
• W3C WML community group - WebMCP GitHub repo (specification + issues)
• Forbes - Google Ships WebMCP, The Browser-Based Backbone For The Agentic Web (19 Feb 2026)
• Webfuse - WebMCP practical guide (longest treatment of the protocol mechanics in 2026)
• Semrush - WebMCP for marketers and SEOs (visibility-focused angle)
• dev.to - Chrome's WebMCP early preview walkthrough