Standards and browser support 

The specification 

  • Confirmed: WebMCP is a Draft Community Group Report of the W3C Web Machine Learning Community Group (latest draft: 2 October 2026). It is not a W3C Standard and not on the W3C Standards Track.
  • Confirmed: the entry point is document.modelContext . Tools are registered one at a time with registerTool(tool, { signal }) and unregistered by aborting that AbortSignal; there is no unregisterTool(). provideContext() and clearContext() were removed from the specification (PR #132).
  • Confirmed: tool annotations are readOnlyHint, untrustedContentHint, consequentialHint and debugging (all boolean). See Writing tools for how this extension sets them.
  • Confirmed: the declarative (HTML form) API is still a TODO in the specification; only a separate explainer exists. This extension does not use it.
  • Confirmed: open proposals may still change the API, among them renaming execute to run (#158) and returning the registered tool from registerTool() (#234). The runtime already accepts any return value of registerTool().

Browsers 

Browser Status Confidence
Chrome Origin trial for desktop, milestones 149–156. Behind the flag chrome://flags/#enable-webmcp-testing for local testing. A default shipping milestone is not set on chromestatus. Confirmed (shipping date unconfirmed)
Microsoft Edge Origin trial, expiring 2027-03-30. Confirmed
Brave Experimental. Unconfirmed
Firefox Mozilla standards position: neutral. Confirmed (position label)
Safari / WebKit WebKit standards position: oppose. Confirmed (position label)

There is no cross-browser consensus. Expect WebMCP to be available only in Chromium-based browsers, and only for some visitors, for the foreseeable future.

Agents 

  • Confirmed: the built-in browser of the ChatGPT desktop app uses WebMCP site tools. It only discovers tools of the top-level document (not iframes), runs a safety review per call and requires specific plans and models — see OpenAI's documentation below.
  • Unconfirmed: support in Gemini in Chrome has been announced but not confirmed by a primary source at the time of writing.

What this means for site operators 

  • Treat WebMCP as progressive enhancement. Every page must work fully without it — most visitors' browsers do not offer the API.
  • The extension does nothing when the API is missing: no errors, no console output, no changes to the page.
  • Because the specification can still change, keep the extension up to date; until version 1.0.0 its API may change between minor versions.

Sources 

Primary sources:

Secondary source (not independently confirmed):

  • @mcp-b/webmcp-polyfill package description and changelog of the related @mcp-b packages (navigator alias deprecation)