WebMCP gives websites a structured tool layer for browser agents

October 9 update: Microsoft Edge's live WebMCP origin-trial registration page now lists March 30, 2027 as its expiration, extending the earlier November 17, 2026 date reflected in BTN's October 8 update. This provides more time for controlled trials, but is not stable browser support or a guarantee of eventual standardization.

On August 25, OpenAI made WebMCP materially more accessible to builders by launching its WebMCP Challenge and documenting site tools in ChatGPT’s desktop built-in browser. WebMCP is a proposed open web standard available through a Chrome origin trial: a page can register named tools with descriptions and JSON input schemas, and a compatible browser exposes those tools to the user’s agent. A further platform-level step landed in WordPress Playground in early September. WordPress says a WebMCP proxy merged on September 3 advertises tools registered inside Playground’s nested WordPress iframe on the outer page and forwards calls back into WordPress. Its September 5 developer guidance documents built-in Playground tools for PHP execution, requests, navigation, filesystem and site management, while plugins can expose their own tools through the same path. Microsoft Edge now also lists WebMCP as an active origin trial, with the trial scheduled to expire March 30, 2027. That moves the browser side beyond Chrome alone, although both implementations remain experimental rather than stable cross-browser web-platform support.

Browser agents are usually forced to operate a website as if they were a human with a mouse and keyboard. That makes automation slow and fragile when layouts change, elements are ambiguous or multi-step state is hard to infer. WebMCP lets the website declare what actions are available and execute them inside the page’s own application logic and signed-in session. WordPress Playground demonstrates how that model can work even when the actual application lives inside an embedded runtime: plugin tools can be surfaced across the iframe boundary without a separate remote MCP server. For SaaS, CMS and web-product builders, that turns WebMCP from an abstract browser API into an integration pattern that platforms can adopt and extend. Edge joining the experiment is a meaningful interoperability signal: builders can now test the same proposed site-tool layer in two Chromium-family browsers instead of treating it as a Chrome-only trial. It still does not establish support from Firefox or Safari, nor guarantee that the API will ship unchanged.

The Edge trial extension changes the test window rather than WebMCP's maturity: teams now have until March 30, 2027 on the published trial page to evaluate the browser-side API, subject to Microsoft's terms and possible changes. It does not imply Firefox/Safari support.

WebMCP’s imperative API lets a page register tools through `document.modelContext.registerTool()`. Each tool has a name, description, JSON input schema and an execution handler. Chrome also documents a declarative path for suitable form interactions. A compatible agent sees the structured contract rather than reverse-engineering what a button or field probably does.

OpenAI documents site tools in the ChatGPT desktop app’s built-in browser. When a supported page exposes a matching WebMCP tool, ChatGPT can discover it while the page is open, operate within the same live signed-in session and ask for website-access permission before continuing.

Playground runs WordPress inside a nested iframe, which would normally hide tools registered inside the embedded page from an agent inspecting the top-level document. WordPress says its WebMCP proxy, merged September 3, advertises those inner tools on the outer Playground page and forwards invocations back into WordPress. Plugins can wrap WordPress abilities or application actions as WebMCP tools and make them discoverable without running a separate WebMCP server.

WordPress documents built-in tools for executing PHP, making requests, reading and writing files, navigating, querying site information and managing saved Playground sites. This turns a browser-hosted WordPress instance into a directly manipulable development environment for a compatible agent while keeping the work visible in the live UI.

Chrome’s implementation remains an origin trial and local-development flag rather than a stable cross-browser API. The current interface uses `document.modelContext`; the earlier `navigator.modelContext` form was already deprecated in Chrome 150, showing that the API can still move. Chrome’s documentation also adds lifecycle, cancellation and cross-origin controls.

WebMCP borrows the tool-oriented idea familiar from Model Context Protocol but places the capability inside the current web page and browser session. WordPress Playground supports both approaches: its older MCP path uses a local Node.js server and WebSocket bridge, while WebMCP exposes actions through the browser page itself.

A WebMCP action may search, edit, submit, purchase or mutate state, depending on what the website exposes. Builders need narrow schemas, clear descriptions, server-side authorization and human confirmation for consequential actions. Embedded platforms also need to treat tool delegation across iframe and origin boundaries as a capability boundary.

Microsoft's Edge Origin Trials catalogue now lists WebMCP as an active trial expiring March 30, 2027. Sites can register a domain for the trial, giving WebMCP a second browser-vendor test surface alongside Chrome. Because Edge and Chrome are both Chromium-family browsers and the API remains experimental, this is progress toward interoperability rather than evidence of a settled cross-browser standard.

Microsoft's live Edge Origin Trials registration page now gives March 30, 2027 as the WebMCP trial expiration, replacing the previously published November 17, 2026 date. Registration remains domain-based and experimental; the trial terms warn of instability, possible termination and the need for feature detection and graceful degradation. Builders can use the longer window for interoperability tests, not as a production stability guarantee.