@redscope-ai/mcp-chrome-bridge
v1.0.0
Published
RedScope-scoped Chrome MCP bridge compatibility package
Maintainers
Readme
@redscope-ai/mcp-chrome-bridge
RedScope-scoped compatibility package for the Chrome MCP bridge.
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 publicCompatibility boundaries:
- Keep the existing
mcp-chrome-bridgeandmcp-chrome-stdiobin 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=1to skip automatic native-host setup during RedScope postinstall. CLAUDE_CODE_SKIP_CHROME_MCP_SETUP=1is still accepted as a legacy compatibility alias.
