WebMCP: what changed, and what is true today

A dated changelog with a source for every line. Sources checked daily; last checked , last change .

Independent. This site is not affiliated with, endorsed by or sponsored by the W3C, the W3C Web Machine Learning Community Group, Google, Chrome, Microsoft or any browser vendor. WebMCP is a Community Group draft, not a W3C Standard. Always check the linked primary sources.

Current state

Spec status"Draft Community Group Report, 13 November 2026". Not a W3C Standard and not on the Standards Track.
Source: spec · verified 2026-11-17
API entry pointdocument.modelContext. The getter moved from Navigator to Document on 2026-05-27, so older posts that use navigator.modelContext are out of date.
Source: commit c7b5c70 · verified 2026-11-17
Declarative (HTML form) APIRemoved from the spec on 2026-10-08 "for now". Chrome's docs page (last updated 2026-10-07) still describes it.
Sources: commit 14ae813, Chrome docs · verified 2026-11-17
Chrome origin trialStarted in Chrome 149; approved for M149 to M156, extended to M162 (record created 2026-09-28). Chrome Platform Status still says "Proposed", with TAG, security and privacy reviews "Pending". Chrome has not published a calendar end date in the sources we can read.
Sources: Chrome Platform Status (JSON), Blink intent · verified 2026-11-17
Edge origin trialTrial expiration date shown by Microsoft: March 30, 2027.
Source: Edge origin trials · verified 2026-11-17
Other browsersWebKit: oppose (closed 2026-06-11). Mozilla: neutral (closed 2026-08-05).
Sources: WebKit #670, Mozilla #1412 · verified 2026-11-17
Who calls toolsChrome's docs name its example extensions (the Example Agentic Chrome Extension and the Model Context Tool Inspector) and say they are separate from Gemini in Chrome. The spec repo lists Brave's Leo AI chat as default-on. We have not confirmed any other consumer.
Sources: Chrome docs, commit 56b8e7a · verified 2026-11-17
Latest spec commit4c7ed44, 2026-11-13, "Update continuations explainer to match the implementation in Blink. (#381)". The repo has no tagged releases.
Source: commit history · verified 2026-11-17
LighthouseHas WebMCP audits in an "agentic browsing" category since v13.2.0, on by default since v13.3.0. Latest release v13.6.0 (2026-10-27).
Source: Lighthouse releases · verified 2026-11-17

Changelog

Newest first. Dates are UTC commit or page dates. Commit links point to the full commit. "What it breaks" is our plain-language reading of the change; where it is an inference the line says "likely" or "inference". Lighthouse release pages show only day and month, so the year is inferred from the release order. We publish nothing we cannot cite, and leave out changes we could not verify.

· Brave Leo AI chat: WebMCP support now default

Spec repo implementation-status update, "Update Leo AI chat WebMCP support from experimental to default (#383)".

Nothing. A status note, and the first non-Google consumer the repo lists as default-on (the repo's own claim, not independently tested).

Source: commit 56b8e7a

· getTools() traversable scope described

"Describe the traversable scope of getTools() (#382)".

Agents that assume getTools() returns tools from every frame (inference); the spec now defines which documents are included.

Source: commit 0c3e712

· toolactivated event fires after execute

"Fire toolactivated event after invoking execute (#371)".

Nothing existing; it is a new event. Code that built its own activation signal may now double-count (inference).

Source: commit f2f2ae2

· outputSchema added to tools

"Add outputSchema to ModelContextTool and RegisteredTool (#254)".

Nothing; additive. Validators and linters need to know the new field.

Source: commit 6cd745a

· Cross-origin tool exposure needs a two-sided opt-in

"Document cross-origin tool exposure and two-sided opt-in in Section 6.3.4 (#326)". Lighthouse v13.6.0 shipped the same day; its WebMCP lines are smoke-test changes only.

Embedders that expect an iframe's tools to reach the parent without the iframe opting in (inference from the title).

Source: commit 6838130 · Lighthouse v13.6.0

· Declarative (HTML form) API removed from the spec

"Remove declarative API from the spec for now (#338)". Chrome's docs page (last updated 2026-10-07) still documents it.

Sites and checkers that rely on declarative form annotations now have no spec text to cite. Lighthouse's webmcp-form-coverage audit still exists in v13.6.0.

Source: commit 14ae813 · Chrome docs

· Chrome origin trial extended from M156 to M162

Chrome Platform Status extension stage created 2026-09-28: last desktop milestone 162. Reason given: "OT feedback has suggested improvements to the API, which we are implementing." The base trial was M149 to M156.

Nothing; trial tokens stay useful longer. No calendar end date is published in the sources we can read.

Source: Chrome Platform Status (JSON)

· Lighthouse 13.5.0: tool-count warning, getTools() fixture

"webmcp-registered-tools: warn when exceeding recommended limit"; "webmcp-form-coverage: pass instead of n/a when all forms covered"; "webmcp: support document.modelContext.getTools in fixture". The release page shows "18 Sep"; the year is inferred.

Pages that register many tools now get a Lighthouse warning.

Source: Lighthouse v13.5.0

· debugging member added to ToolAnnotations

"Add debugging member to ToolAnnotations (#253)".

Nothing; additive annotation.

Source: commit 8a82bb7

· executeTool() input type widened from object to any

"Change executeTool() inputObject type from object to any (#251)".

TypeScript typings, and agents that assumed the input is always an object (inference).

Source: commit 97da8f5

· Spec examples updated to the current modelContext API; local-dev flag documented

"Update stale examples and references to the current modelContext API (#284)" and "Add flag for local development in Chromium browsers (#280)".

Tutorials copied from older examples (for example ones using navigator.modelContext or provideContext) are now out of date.

Source: commit 16861c6 · commit 2092f25

· Lighthouse 13.4.1: gatherers switch to document.modelContext

"webmcp: Refined WebMCP gatherers to check document.modelContext and removed snapshot mode". The release page shows "20 Jul"; the year is inferred.

Pages that only expose the old navigator.modelContext name are likely no longer detected by Lighthouse's WebMCP audits (the release says gatherers check the new name).

Source: Lighthouse v13.4.1

· WebKit position: oppose

WebKit standards-positions issue #670 "WebMCP" closed as completed with the label position: oppose, plus concern labels such as security, privacy, API design and use cases.

Any plan that assumes Safari will implement WebMCP.

Source: WebKit #670

· ModelContextClient removed from the spec

"Remove ModelContextClient for now (#205)".

Tool code written against a ModelContextClient parameter (likely; the title says it was removed).

Source: commit 067a1c9

· Chrome blog: sign up for the WebMCP origin trial

Chrome blog, published June 9, 2026: "In Chrome 149, you can sign up for the WebMCP origin trial." The post names no end date.

Nothing. It is the public start of the origin trial.

Source: Chrome blog

· registerTool() now returns a promise

"Make registerTool() return a promise (#200)". On 2026-06-17: "Reject registerTool() promise when signal is aborted (#202)".

Code that treats registerTool() as synchronous or void; registration errors now surface as rejections (inference).

Source: commit ec37ec4 · commit bc93f03

· modelContext getter moved from Navigator to Document

"Move the modelContext getter to Document (#184)". Preceded on 2026-05-19 by "Scope ModelContext to Document, and handle detached documents (#177)".

Every snippet that calls navigator.modelContext; the spec name is now document.modelContext.

Source: commit c7b5c70 · commit 986f461

· Chrome approves an origin trial for M149 to M156; docs published

Blink-dev "Intent to Experiment: WebMCP" (posted 2026-05-15); reply on 2026-05-18: "LGTM to experiment from M149 to M156 inclusive." The estimated desktop ship was M157. Chrome's docs page shows "Published: May 18, 2026".

Nothing; the trial was later extended to M162 (see 2026-09-28). M157 was Chrome's May estimate, not a commitment.

Source: Blink intent · Chrome docs

· Lighthouse 13.3.0: agentic browsing category on by default

"New agentic browsing category added to default config"; "webmcp: add webmcp smoketests". The release page shows "07 May"; the year is inferred.

Every Lighthouse run now includes an agentic-browsing section for WebMCP.

Source: Lighthouse v13.3.0

· Lighthouse 13.2.0: first WebMCP audits

Adds webmcp-form-coverage, webmcp-registered-tools, webmcp-schema-validity and an agentic browsing category. The release page shows "01 May"; the year is inferred.

Nothing; it is Google's first WebMCP audit tooling.

Source: Lighthouse v13.2.0

· MCP tool-name rules codified; tool title added

"Codify MCP tool name requirements and add tool title (#152)".

Tools whose names do not meet the MCP name requirements (read the commit for the exact rules).

Source: commit 1380910

· registerTool() takes an optional AbortSignal

"registerTool() takes an optional AbortSignal (#147)". The next day: "Remove unregisterTool() from proposal explainer (#156)" (explainer text only).

Explainer-era tutorials that use unregisterTool(); the signal appears to be the documented replacement (inference from the two titles).

Source: commit 6708e33 · commit 90daeee

· provideContext() and clearContext() removed

"Remove provideContext() and clearContext() (#132)".

Any page using provideContext() or clearContext(). Tutorials written before March 2026 still show them.

Source: commit fe84c67

· Chrome opens an early preview; DevTrial on desktop 146

Chrome post, "Published: February 10, 2026": "WebMCP is available for prototyping to early preview program participants." Blink-dev "Ready for Developer Testing: WebMCP" (posted 2026-02-09, DevTrial on desktop 146); a Chrome engineer replied that it is "an early prototype for developer testing and not an intent to to ship."

Nothing. This is the earliest public Chrome milestone we found.

Source: Chrome post · Blink thread

Compatibility table

What the spec says, by feature, with the date it changed. "Chrome" is only filled where a Chrome source says so; we do not have a verified feature-by-Chrome-version matrix, and we say "not verified" rather than guess.

FeatureSpec status (2026-11-17)ChangedChrome / toolsSource
document.modelContextCurrent entry point2026-05-27Lighthouse checks it since v13.4.1 (2026-07-20). Chrome version: not verifiedcommit, Lighthouse
navigator.modelContextOld name (spec text of Feb 2026)moved 2026-05-27Not verifiedcommit 3e1d68b
provideContext(), clearContext()Removed2026-03-05Not verifiedcommit
registerTool()Returns a promise; optional AbortSignal2026-03-26, 2026-06-08Not verifiedcommit
Declarative (HTML form) APIRemoved "for now"2026-10-08Chrome docs still document it; Lighthouse still audits form coveragecommit, docs
outputSchemaAdded2026-11-02Not verifiedcommit
toolactivated eventAdded2026-11-09Not verifiedcommit
getTools()Scope defined2026-11-11Lighthouse fixture supports it (v13.5.0)commit

Browser and vendor positions

WhoPosition / statusDateSource
ChromeOrigin trial M149 to M162; status "Proposed"; reviews pending2026-09-28 (extension)Chrome Platform Status
EdgeOrigin trial, expires March 30, 2027checked 2026-11-17Edge trials
Safari / WebKitOppose2026-06-11#670
Firefox / MozillaNeutral2026-08-05#1412
Brave (Leo AI chat)Default-on, per the spec repo2026-11-12commit

For AI agents: this page has WebMCP tools

In a browser with WebMCP enabled, this page registers three read-only tools on document.modelContext (or navigator.modelContext in Chrome's origin trial builds):

They read only this page and its feed, change nothing, and send nothing anywhere. Source: webmcp.js. Useful as a live example if you are building your own tools.

FAQ

Is it navigator.modelContext or document.modelContext?

The spec moved the getter to Document on 2026-05-27, and Lighthouse checks document.modelContext since v13.4.1. Many tutorials still show navigator.modelContext. See the entry.

Is the declarative (form) API gone?

It was removed from the spec on 2026-10-08 "for now". The spec repo says it is being explored; Chrome's docs page still describes it. Treat it as unstable. See the entry.

When does the Chrome origin trial end?

Chrome Platform Status shows the trial running to Chrome 162 after a 2026-09-28 extension. We could not find a calendar end date from Chrome. Edge's trial page says March 30, 2027.

Will Safari or Firefox ship it?

WebKit's recorded position is oppose (2026-06-11); Mozilla's is neutral (2026-08-05). Neither is a ship decision. Positions can change; check the issues linked in the table.

Who actually calls my tools?

Chrome's docs name its own example extensions, and say they are separate from Gemini in Chrome. The spec repo lists Brave's Leo AI chat as default-on. We have not confirmed other consumers, and we do not claim any.

Is it a W3C standard?

No. It is a Draft Community Group Report from the W3C Web Machine Learning Community Group. Community Group drafts are not on the W3C Standards Track.

Does Lighthouse test WebMCP?

Yes. Since v13.2.0 (2026-05-01) it has WebMCP audits in an agentic browsing category, on by default since v13.3.0. This site is not a checker and scans no sites.

How does this site stay accurate?

Each entry cites a primary source. Each line in the current-state box carries a "verified" date. If we cannot verify a claim, we leave it out. Spotted a mistake? Check the cited source first; corrections are published as new dated entries.