[BUG] claude-in-chrome MCP: tabs_context_mcp always returns "Browser extension is not connected" despite extension showing connected

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

MCP server shows connected in /mcp panel, Chrome extension UI also shows connected, but every call to tabs_context_mcp returns "Browser extension is not connected".

What Should Happen?

Environment:

• macOS Darwin 23.3.0
• Claude Code CLI (latest)
• Chrome extension installed and enabled

Error Messages/Logs

~/Library/Logs/Claude*/chrome-native-host.log shows socket created and listening, but no client ever connects:                                                                                                                    
  Socket created successfully at: /tmp/claude-mcp-browser-bridge-builder/26774.sock                                                                                                                                                 
  Entering main message loop                                                       
  Socket server listening for connections

Steps to Reproduce

1. Open Chrome, confirm extension shows connected
2. In Claude Code, /mcp shows claude-in-chrome · connected
3. Call tabs_context_mcp → always fails
4. Restarting Chrome, Claude Code, and reconnecting via /mcp all have no effect

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.109 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_