WebMCP

WebMCP is a specification from the W3C Web Machine Learning Community Group that defines a JavaScript API allowing web applications to expose their functionality as tools that AI agents, browser-native agents, and assistive technologies can discover and invoke. In essence, any web page implementing WebMCP becomes a Model Context Protocol server — but one that runs entirely in client-side script rather than on a backend. This represents a fundamental shift in how agents interact with the web: instead of scraping DOM elements and simulating clicks, agents can call structured, schema-described functions that the application itself has deliberately exposed.

From Screen-Scraping to Semantic Tool Use

The current generation of browser-based AI agents — products like Claude in Chrome, ChatGPT Operator, or Google's Project Mariner — interact with web applications by reading the visual layout and clicking interface elements much as a human would. This works, but it is fragile, slow, and limited to whatever the UI happens to expose. WebMCP inverts this relationship. A web developer registers tools through navigator.modelContext.registerTool(), providing a name, a natural-language description, a JSON Schema for input parameters, and an execute callback. The agent can then discover these tools, understand what they do, and invoke them directly — no pixel-hunting required.

This is the same architectural pattern that tool use and function calling established for LLM-to-API communication, now extended to the browser itself. Where MCP standardized how desktop applications and cloud services expose capabilities to AI models, WebMCP does the same for the billions of existing web applications — making the entire web a composable surface for agentic engineering.

How It Works

The API extends the browser's Navigator interface with a modelContext object. Web developers register tools imperatively through JavaScript or (in the specification's planned declarative mode) through HTML form annotations that are automatically synthesized into tool definitions. Each registered tool includes a structured inputSchema following JSON Schema, enabling agents to understand exactly what parameters are expected and validate their calls before execution.

Critically, WebMCP includes a ModelContextClient interface that allows tools to request user interaction during execution — for instance, showing a confirmation dialog before completing a purchase. This preserves the human-in-the-loop principle that distinguishes collaborative agentic workflows from fully autonomous ones, and reflects the same design philosophy behind agent orchestration patterns that maintain human oversight at critical decision points.

Composability and the Agentic Web

WebMCP's deepest implication is for composability. When every web application can declare its capabilities as structured tools, the browser becomes a universal multi-agent substrate. A personal agent coordinating a complex task — booking travel, comparing insurance quotes, managing a project — can discover and compose tools from multiple web applications in a single session, maintaining shared context through agentic memory while the user watches and intervenes when needed.

This vision aligns directly with the agentic web: a web where pages are not just documents to be read or interfaces to be clicked, but programmable services that agents can orchestrate. WebMCP provides the missing protocol layer that connects the browser's rendering engine to the agent's reasoning engine, turning the world's largest application platform into a tool catalog.

Implications for Discovery and Commerce

For businesses, WebMCP changes the economics of discovery. When agents can semantically query what a web application does rather than parsing its visual interface, the quality and specificity of tool descriptions become a competitive advantage — a new dimension of Generative Engine Optimization. In agentic commerce, WebMCP-enabled storefronts can expose product search, price comparison, and checkout as structured tools, allowing buyer agents to transact directly without navigating UI flows designed for human attention spans.

The specification is still in active development as of early 2026, with security considerations (the API requires a secure context) and the declarative form-based mode still being finalized. But the trajectory is clear: just as open standards like HTTP turned the web from a document repository into an application platform, WebMCP positions it to become an agent platform — a surface where human and artificial intelligence collaborate through shared, structured interfaces.