About this integration
Your real, logged-in Chrome as an MCP server: 59 token-efficient web-dev tools. ChromeOS included.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.17.0
- Package
- chrome-bridge-mcp
- Last compatibility test
- Not independently tested
Connect your agent
chrome-bridge-mcpPublisher README and manifest reviewed from pinned captures; package and upstream service were not executed or independently security-audited.
Capabilities: browser automation, page inspection, network tooling, screenshots
Connected profiles
Additional details
io.github.frsorrentino/chrome-bridge
Source ↗ · Checked 2026-09-171.17.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17chrome-bridge-mcp
Source ↗ · Checked 2026-09-191.17.0
Source ↗ · Checked 2026-09-19The documented architecture connects Claude Code to the MCP server over stdio.
Source ↗ · Checked 2026-09-19The loopback bridge can run without a token; CHROME_BRIDGE_TOKEN secures extension and relay handshakes and is required off-loopback.
Source ↗ · Checked 2026-09-19Register the local server entrypoint with the MCP client.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19