Choose in order
- Does the target browser provide the WebMCP behavior you need? Check WebMCP resources and status. If yes, you may not need a runtime package.
-
Do you only need ambient types for the live proposal? Use the Community Group’s
webmcp-typespackage, which Chrome’s Imperative API guide also recommends.@mcp-b/webmcp-typesis deprecated and only forwards it. -
Do you need MCP-B adapter extensions or schema conversion? Use
@mcp-b/webmcp-ts-sdk. -
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-polyfillor@mcp-b/globaluntil it does. -
Do you need MCP bridge transport,
listTools, prompts, resources, or direct MCP server access? Use@mcp-b/global. -
Do you only need React tool registration with JSON Schema input? Use
usewebmcp. -
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 polyfilleddocument.modelContext, and client/provider hooks use their configured MCP connection.
Package comparison
Continue with the selected path
- For native behavior and ambient proposal types, use the WebMCP API sources.
- For the standalone polyfill, follow the
@w3c/webmcp-polyfillREADME and the first tool tutorial. - For the full MCP-B runtime, follow the
@mcp-b/globaloverview and reference. - For React, compare
usewebmcpwith@mcp-b/react-webmcp, then use the React tutorial. - For MCP-B adapter extensions and schema conversion, use the
@mcp-b/webmcp-ts-sdkreference.
