The root RedScope package depends on this RedScope-scoped package boundary instead of directly depending on the legacy bridge. This package still delegates to the existing @claude-code-best/mcp-chrome-bridge registry package for now, so behavior remains unchanged until the bridge implementation is forked, vendored, or republished under the RedScope scope.

This package is publishable as a public compatibility shim. A first release can be cut after logging in to an npm account that can publish under the @redscope-ai scope:

npm publish --access public

Compatibility boundaries:

Keep the existing mcp-chrome-bridge and mcp-chrome-stdio bin names.
Preserve the upstream CLI argument surface.
Do not change Chrome native-host registration behavior in this shim.

Setup environment:

Prefer REDSCOPE_SKIP_CHROME_MCP_SETUP=1 to skip automatic native-host setup during RedScope postinstall.
CLAUDE_CODE_SKIP_CHROME_MCP_SETUP=1 is still accepted as a legacy compatibility alias.