Share Your Local Browser With Cloud AI Agents via Chrome DevTools MCP

Cloud agents fail on real browser work for two reasons:

• they cannot reach your local Chrome from remote runtimes
• multiple agents conflict when sharing one DevTools connection

@vibebrowser/chrome-devtools-mcp solves this with StreamableHTTP transport, per-session isolation, and optional Tailscale routing.

Quick install

npx @vibebrowser/chrome-devtools-mcp install --port 9333

npx @vibebrowser/chrome-devtools-mcp install --port 9333 --tailscale

Key facts

• Package: @vibebrowser/chrome-devtools-mcp
• Tailscale flag is --tailscale (not --tailnet)
• Uses StreamableHTTP transport with per-session isolation
• Connects via DevToolsActivePort (no --remote-debugging-port required)
• Avoids common debug-port bot-detection signals
• Auto-configures Claude Code, Copilot CLI, and OpenCode
• Health endpoint: GET /health
• For remote/cloud agents, replace localhost with your Tailscale hostname
• MagicDNS must be enabled on your tailnet for HTTPS hostname routing

Agent config examples

Claude Code

{"mcpServers":{"chrome-devtools":{"url":"http://localhost:9333/mcp"}}}

Copilot CLI

{"mcpServers":{"chrome-devtools":{"url":"http://localhost:9333/mcp"}}}

OpenCode

{"mcp":{"chrome-devtools":{"url":"http://localhost:9333/mcp"}}}

Remote example:

https://your-machine-name.your-tailnet.ts.net:9333/mcp

Links

• npm: https://www.npmjs.com/package/@vibebrowser/chrome-devtools-mcp
• GitHub: https://github.com/dzianisv/chrome-devtools-mcp

Done: one install command gives cloud AI agents stable local Chrome access with isolated sessions.