Feature: Add list_browsers and get_browser_info tools to Chrome extension MCP
Problem
When the Claude in Chrome extension is installed on multiple machines (e.g., a Windows dev server and an Ubuntu workstation), there is no way to:
- List all connected browser instances — you only discover other browsers when
tabs_context_mcpfails with "Multiple Chrome extensions connected" - Identify which browser you're currently connected to — there's no
get_browser_infotool; the browser name only appears inswitch_browserresponses - Choose a specific browser by name —
switch_browserbroadcasts to all extensions and connects to whichever one clicks "Connect" first (a race condition)
This creates a poor experience in multi-machine setups where the same user has Chrome + Claude extension running on 2+ machines simultaneously.
Current Behavior
tabs_context_mcp → "Multiple Chrome extensions connected" (error, no info about which browsers)
switch_browser → broadcasts, first click wins, returns "Connected to browser X"
No way to enumerate, no way to target.
Proposed Solution
Add two new MCP tools:
list_browsers
Returns all currently connected Chrome extension instances with metadata:
{
"browsers": [
{ "id": "abc123", "name": "dev.lab.ergonet.pl", "connected": true },
{ "id": "def456", "name": "Chrome on logi.ergonet.pl", "connected": false }
],
"current": "abc123"
}
get_browser_info
Returns info about the currently connected browser:
{
"id": "abc123",
"name": "dev.lab.ergonet.pl",
"userAgent": "Chrome/145.0...",
"platform": "Win32"
}
Optional: connect_browser (by name/id)
Allow targeting a specific browser without broadcasting:
connect_browser(name="dev.lab.ergonet.pl")
Use Case
Multi-machine development setup:
- Machine A (Windows Server) — primary Claude Code workstation
- Machine B (Ubuntu) — secondary browser for testing/monitoring
Both have Chrome + Claude extension. Today, starting a Claude Code session is a coin flip on which browser connects. With list_browsers, the agent can see both and connect to the correct one deterministically.
Environment
- Claude Code CLI on Windows Server 2025
- Chrome 145 with Claude extension on 2 machines
superpowers-chromeplugin enabled
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗