Choose a runtime

​

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.
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 @mcp-b/webmcp-polyfill.
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

• For native behavior and ambient proposal types, use the WebMCP API sources.
• For the standalone polyfill, follow the @mcp-b/webmcp-polyfill overview and first tool tutorial.
• For the full MCP-B runtime, follow the @mcp-b/global overview and reference.
• For React, compare usewebmcp with @mcp-b/react-webmcp, then use the React tutorial.
• For MCP-B adapter extensions and schema conversion, use the @mcp-b/webmcp-ts-sdk reference.

​

How the layers relate