Claude in Chrome: Browser extension fails to connect (MCP bridge)

Description

The mcp__claude-in-chrome browser automation tools consistently fail with:

Browser extension is not connected. Please ensure the Claude browser extension is installed and running...

This happens despite the extension being installed and the user being logged in.

Environment

• OS: macOS (Darwin 24.6.0)
• Claude Code model: claude-opus-4-6
• Browser: Comet (Chromium-based)
• Extension: Claude browser extension (latest)

Steps to Reproduce

1. Start a Claude Code session
2. Call tabs_context_mcp with createIfEmpty: true
3. Get error: "Browser extension is not connected"

Expected Behavior

The MCP bridge should connect to the browser extension and return tab context.

Actual Behavior

Every call to any mcp__claude-in-chrome__* tool returns the "not connected" error. No tabs are returned, no browser automation is possible.

Notes

• This has been an intermittent issue across multiple sessions
• Restarting Chrome/the extension sometimes helps, sometimes doesn't
• The connection was working in prior sessions on the same setup

Labels

bug, claude-in-chrome