@mcp-b/webmcp-polyfill
supplies the package-supported document.modelContext surface.
@mcp-b/webmcp-ts-sdk adds BrowserMcpServer, which mirrors core tool
operations while providing MCP-B-only capabilities. @mcp-b/global
initializes those layers and connects the selected browser transport.
Global initialization preserves the browser-shaped programming model:
1. Browser context
A native implementation or
@mcp-b/webmcp-polyfill supplies the browser surface.2. MCP-B runtime
BrowserMcpServer mirrors core tools, adds MCP-B extensions, and becomes
document.modelContext.3. Selected transport
The transport connects explicit MCP clients without changing page code.
document.modelContext normally, whether the active implementation is
native, polyfilled, or wrapped by MCP-B. Cleanup restores the property
descriptors that existed before wrapping; it does not uninstall the separately
owned polyfill.
This separation allows a library to depend only on types, a site to use only
the tool-only polyfill, or an application to install the complete MCP-B runtime.
Core tool registrations remain visible to native browser tooling, while
cleanup can restore the context that existed before initialization.
navigator.modelContext remains only as a deprecated compatibility alias. New
integrations use document.modelContext.
See the @mcp-b/global reference and Choose a
runtime.