Learn about the proposal
The Community Group draft owns the proposed JavaScript API. Chrome maintains the current developer overview, user journey guide, and WebMCP and MCP comparison. The WebMCP API sources and declarative API sources route implementation questions to their upstream owners. WebMCP resources and status collects status, security, inspection, and testing resources.Where MCP-B fits
The Community Group publishes the official polyfill,@w3c/webmcp-polyfill, and the
webmcp-types TypeScript
declarations. MCP-B provides packages that connect pages to MCP, including the
@mcp-b/global runtime, React bindings, transports, iframe bridges, and a local
relay. Bridges can make page
tools available to MCP clients, but the browser document remains the execution
environment. MCP-B does not define the WebMCP proposal.
WebMCP and MCP-B
extensions explains which
behavior belongs to this project. Transports and
bridges explains how those
packages cross browser boundaries.