Skip to main content
Start with the live WebMCP proposal and current browser support. Use the official W3C packages for the standard API. Add MCP-B packages when the page must reach MCP clients or needs MCP features.

Choose in order

  1. Does the target browser provide the WebMCP behavior you need? Check WebMCP resources and status. If yes, you may not need a runtime package.
  2. Do you only need ambient types for the live proposal? Use the Community Group’s webmcp-types package, which Chrome’s Imperative API guide also recommends. @mcp-b/webmcp-types is deprecated and only forwards it.
  3. Do you need MCP-B adapter extensions or schema conversion? Use @mcp-b/webmcp-ts-sdk.
  4. Do you need browser tool registration and discovery where native support is unavailable? Use the W3C Community Group polyfill, @w3c/webmcp-polyfill. It does not ship declarative tools yet. If you need declarative tools without native support, use the deprecated @mcp-b/webmcp-polyfill or @mcp-b/global until it does.
  5. Do you need MCP bridge transport, listTools, prompts, resources, or direct MCP server access? Use @mcp-b/global.
  6. Do you only need React tool registration with JSON Schema input? Use usewebmcp.
  7. Do you need Standard Schema input such as Zod, output schemas, or React prompt, resource, or MCP client/provider hooks? Use @mcp-b/react-webmcp. Prompt and resource hooks require @mcp-b/global; tool hooks work with native or polyfilled document.modelContext, and client/provider hooks use their configured MCP connection.

Package comparison

Continue with the selected path

How the layers relate

For the layering rationale, see Runtime Layering. WebMCP and MCP-B extensions describes the package boundary.