Bug: Claude in Chrome MCP server doesn't connect to native host socket (Linux)
Resolved 💬 2 comments Opened Feb 16, 2026 by itay-sadov Closed Feb 16, 2026
Environment:
- Claude Code 2.1.42 (latest)
- Linux 6.17.0-14-generic
- Chrome extension 1.0.51
- Google Chrome
Problem:
Running claude --chrome starts both the native host (--chrome-native-host) and MCP server (--claude-in-chrome-mcp), but the MCP server never connects to the native host's Unix socket.
/chrome shows Status: Enabled, Extension: Installed, but all mcp__claude-in-chrome__* tool calls return "Browser extension is not connected."
Diagnostics:
- Native host listens on /tmp/claude-mcp-browser-bridge-<user>/<pid>.sock — confirmed with ss -xlp
- MCP server has zero connections to that socket — confirmed with ss -xp
- Native messaging host config at ~/.config/google-chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json is correct and points to valid binary
- Tried: restarting Chrome, restarting Claude Code, /chrome → Reconnect extension, killing stale native host processes — none resolved it
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗