[BUG] Claude in Chrome: MCP client never connects to native host socket despite both sides running

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?

Description:

The claude-in-chrome MCP server in Claude Code consistently returns "Browser extension is not connected" even though the Chrome native messaging host is running
and listening on its socket.

Environment:

• OS: macOS Darwin 25.2.0
• Claude Code model: claude-opus-4-6
• Chrome native host version: 0.1.0
• Date: 2026-02-11

Troubleshooting performed:

• Installed Chrome extension from claude.ai/chrome
• Confirmed logged into claude.ai with same account
• Restarted Chrome multiple times
• Rebooted entire computer
• Ran /mcp in Claude Code multiple times (reports "Reconnected to claude-in-chrome")
• Called tabs_context_mcp multiple times — always returns "not connected"

Key findings from logs:

1. Native host is running and listening (chrome-native-host.log):

• Started at 12:52:06, created socket at /tmp/claude-mcp-browser-bridge-harrisoncannon/6533.sock
• Socket file exists and is valid (srw-------)
• No MCP client has connected since startup — last successful client connection was Feb 10

1. There's a separate "Control Chrome" MCP (mcp-server-Control Chrome.log):

• This server initializes successfully and exchanges JSON-RPC messages
• It exposes different tools (open_url, get_current_tab, etc.) vs the claude-in-chrome tools (tabs_context_mcp, read_page, etc.)
• This suggests two separate Chrome MCP integrations may be conflicting

1. The disconnect pattern: The claude-in-chrome MCP server reports "connected" at the MCP protocol level but cannot reach the Chrome extension through the native

host socket bridge. The socket is listening but the MCP client never connects to it.

Relevant log files:

• /Users/harrisoncannon/Library/Logs/Claude/chrome-native-host.log
• /Users/harrisoncannon/Library/Logs/Claude/mcp-server-Control Chrome.log
• /Users/harrisoncannon/Library/Logs/Claude/mcp.log

Suspected root cause:
The Claude Code claude-in-chrome MCP server starts but fails to discover or connect to the native host's Unix socket (6533.sock). The /mcp reconnect claims
success at the MCP server level, but the server-to-browser bridge (via the native messaging host socket) is never established. Possibly a socket path discovery
issue, or the "Control Chrome" MCP is interfering.

What Should Happen?

After /mcp reports a successful reconnection, tabs_context_mcp should return the current browser tab context.

chrome-native-host.log
mcp-server-Control Chrome.log
mcp.log

Error Messages/Logs

Steps to Reproduce

1. Upgrade Claude Code to latest version
2. Installed Claude browser extension in Chrome
3. Asked Claude Code to help me with something in my browser
4. Can't connect

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

v2.1.39

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_