Home › Guides › WebMCP: Where Chrome’s Web API for AI Agents Stands
✓ checked 28 October 2026 · sources: Chrome Platform Status, blink-dev mailing list, Chromium release schedule, GitHub (WebKit and Mozilla standards positions, W3C TAG, webmachinelearning/webmcp, Playwright) · method · caveats · download the data
WebMCP, a proposed web API that lets websites hand AI agents a list of “tools” to call instead of making them click through pages, is still an experiment in Chrome. Its origin trial was set to run from Chrome 149 to Chrome 156, which became stable on 20 October 2026. On 28 September 2026 the Chrome team asked to extend it to Chrome 162, scheduled for 2 February 2027. Apple’s WebKit team opposes the proposal, and Mozilla’s position is neutral.
Chrome status: ProposedWebKit: opposeMozilla: neutralW3C TAG review: in progress
Why this matters for bots and scrapers
Today, browser agents work sites the way people do: they read the page and simulate clicks and typing. WebMCP would let a site register functions, with names, descriptions and input schemas, that an agent can call directly. That changes the relationship between sites and automated visitors in both directions. In its position, WebKit says WebMCP makes “an agent is driving” an observable fact, so a site could offer agents more than humans or block them, comparing the second case to the “screen-reader-blocking problem”. Mozilla’s position says that “in an adversarial setting” sites could offer tools that do not match what users see, for example to “tar pit automated browsers” or deliver prompt injection.
Chrome’s status
Chrome Platform Status lists WebMCP (feature 5117755740913664) as “Proposed”, not shipped. A developer trial behind a flag began in Chrome 146. Sites can take part in the origin trial by registering for a token. The trial’s stated goal is to understand “the API ergonomics for agentic workflows across various verticals such as web commerce and productivity”.
In the extension request, the Chrome team wrote that trial feedback “has suggested improvements to the API, which we are implementing”. Alex Russell, one of the Blink API owners, replied the same day with an approval “conditional on some summary of developer feedback from the first OT”. Dominic Farolino of the WebMCP team answered on 29 September that the team hopes to request shipping within the extension window, and that “the imperative API is a lot more popular than the declarative one”. The mailing-list archive showed no further replies when we checked.
Other browsers and the W3C TAG
- WebKit (Safari): oppose. The WebKit issue was labelled “position: oppose” on 11 June 2026, with 8 concern labels including privacy, security, duplication and venue. WebKit argues that hard-to-use sites should be fixed in HTML and ARIA, which help users, assistive technology and agents alike.
- Mozilla (Firefox): neutral. Labelled on 5 August 2026. Mozilla called WebMCP “a potentially valuable abstraction” that opens a surface with “too many open questions to wholeheartedly endorse”, and said the name is misleading because “There is no MCP here.”
- W3C TAG: review open. The Technical Architecture Group opened its review on 11 June 2026. On 26 October it posted interim thoughts that it said are “not a resolution comment”. The review carries the label “Missing: Multi-stakeholder support”.
Chrome Platform Status itself still shows “No signal” for both Gecko and WebKit, so it has not caught up with these positions.
Timeline
| Date | Who | Event |
|---|---|---|
| 8 July 2025 | Chrome Platform Status | WebMCP entry created |
| 10 March 2026 | Chrome 146 stable | Developer trial (behind a flag) from this version |
| 28 May 2026 | Standards positions | Proposal authors ask Mozilla and WebKit for positions |
| 2 June 2026 | Chrome 149 stable | Origin trial starts |
| 11 June 2026 | WebKit | Labelled “position: oppose” |
| 11 June 2026 | W3C TAG | Design review opened |
| 5 August 2026 | Mozilla | Labelled “position: neutral” |
| 28 September 2026 | blink-dev | Chrome team asks to extend the origin trial to Chrome 162 |
| 7 October 2026 | Playwright 1.64 | Adds page.webmcp for testing WebMCP tools |
| 20 October 2026 | Chrome 156 stable | Last version in the original trial window |
| 26 October 2026 | W3C TAG | Posts interim thoughts; review not finished |
| 2 February 2027 | Chrome 162 stable (scheduled) | Last version in the requested extension |
The proposal lives in the W3C Web Machine Learning Community Group’s webmcp repository on GitHub, which had 4,787 stars, 336 forks and 136 open issues and pull requests on 28 October. Microsoft’s Playwright testing tool added support for listing and calling a page’s WebMCP tools in version 1.64.
For other standards work on AI agents, see IETF AI agent drafts and the Web Bot Auth tracker. For download trends in agent browser tools, see agent-browser vs Playwright.
Method
We read the Chrome Platform Status API entry for WebMCP, the blink-dev “Intent to Extend Experiment” thread on mail-archive.com, Chromium’s milestone schedule, and the GitHub API for the WebKit (issue 670) and Mozilla (issue 1412) standards-positions issues, the W3C TAG review (issue 1238), the webmcp repository and the Playwright v1.64.0 release, all on 28 October 2026. Label dates come from each issue’s timeline.
Caveats
- A browser’s standards position is not a promise about what it will ship, and positions can be revisited. Mozilla’s issue discusses a possible refreshed position.
- Whether the extension request has met Chrome’s conditions is not recorded publicly. Chrome Platform Status lists the extension stage to Chrome 162.
- Microsoft Edge runs its own origin trials; we did not check Edge’s dates.
- GitHub star counts measure interest from developers, not use by sites.
Download the data
- WebMCP timeline (CSV), July 2025 to February 2027.
Cite as: ProxyPicker, “WebMCP: Where Chrome’s Web API for AI Agents Stands”, 28 October 2026, https://proxypicker.com/webmcp-status/.
Press & data requests: email [email protected] for interviews, the raw data behind this page, or corrections. See also our contact page.