What changed
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 already 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. OpenAI says ChatGPT site tools implement WebMCP and can be discovered by ChatGPT in its built-in browser; Chrome exposes the same proposed standard through its experimental implementation. The result is a shared path for agent-native web actions that does not require the agent to infer every step from screenshots or DOM clicks.
Why it matters
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. For SaaS and web-product builders, that creates a new integration surface: instead of maintaining a separate external API solely for agents, they can progressively expose selected user-facing capabilities directly from the live web application. The trade-off is that these tools can perform real actions with real user state, so permissions, confirmation, untrusted content and tool design become part of browser security rather than merely UX.
The website defines the contract
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.
ChatGPT now provides a real client path
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. OpenAI also says ChatGPT Work and Codex can use WebMCP-enabled site tools in supported browser workflows.
Chrome is still treating WebMCP as experimental
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 August documentation also adds lifecycle, cancellation and cross-origin controls, including Permissions Policy and explicit origin exposure for tools in embedded contexts.
This is different from a remote MCP server
WebMCP borrows the tool-oriented idea familiar from Model Context Protocol but places the capability inside the current web page and browser session. That is distinct from exposing a standalone remote MCP server. A site can therefore use its existing frontend state, authentication and application code, while the browser mediates discovery and invocation for the user’s agent.
Tool safety becomes application security
A WebMCP action may search, edit, submit, purchase or mutate state, depending on what the website exposes. Builders need narrow schemas, clear descriptions, appropriate read-only or untrusted-content annotations, server-side authorization and human confirmation for consequential actions. Chrome also restricts WebMCP to origin-isolated documents and gates cross-origin use through the `tools` Permissions Policy.