Claude in Chrome MCP Troubleshooting
Use this skill when Claude in Chrome MCP tools fail to connect or work unreliably.
When to Use
mcp__claude-in-chrome__*tools fail with "Browser extension is not connected"- Browser automation works erratically or times out
- After updating Claude Code or Claude.app
- When switching between Claude Code CLI and Claude.app (Cowork)
- Native host process is running but MCP tools still fail
When NOT to Use
- Linux or Windows users - This skill covers macOS-specific paths and tools (
~/Library/Application Support/,osascript) - General Chrome automation issues unrelated to the Claude extension
- Claude.app desktop issues (not browser-related)
- Network connectivity problems
- Chrome extension installation issues (use Chrome Web Store support)
The Claude.app vs Claude Code Conflict (Primary Issue)
Background: When Claude.app added Cowork support (browser automation from the desktop app), it introduced a competing native messaging host that conflicts with Claude Code CLI.
Two Native Hosts, Two Socket Formats
Why They Conflict
-
Both register native messaging configs in Chrome:
com.anthropic.claude_browser_extension.json→ Claude.app helpercom.anthropic.claude_code_browser_extension.json→ Claude Code wrapper
-
Chrome extension requests a native host by name
-
If the wrong config is active, the wrong binary runs
-
The wrong binary creates sockets in a format/location the MCP client doesn't expect
-
Result: "Browser extension is not connected" even though everything appears to be running
The Fix: Disable Claude.app's Native Host
If you use Claude Code CLI for browser automation (not Cowork):
If you use Cowork (Claude.app) for browser automation:
You cannot use both simultaneously. Pick one and disable the other.
Toggle Script
Add this to ~/.zshrc or run directly:
Usage: chrome-mcp-toggle then restart Chrome (and Claude Code if switching to CLI).
Quick Diagnosis
Critical Insight
MCP connects at startup. If the browser bridge wasn't ready when Claude Code started, the connection will fail for the entire session. The fix is usually: ensure Chrome + extension are running with correct config, THEN restart Claude Code.
Full Reset Procedure (Claude Code CLI)
Other Common Causes
Multiple Chrome Profiles
If you have the Claude extension installed in multiple Chrome profiles, each spawns its own native host and socket. This can cause confusion.
Fix: Only enable the Claude extension in ONE Chrome profile.
Multiple Claude Code Sessions
Running multiple Claude Code instances can cause socket conflicts.
Fix: Only run one Claude Code session at a time, or use /mcp to reconnect after closing other sessions.
Hardcoded Version in Wrapper
The wrapper at ~/.claude/chrome/chrome-native-host may have a hardcoded version that becomes stale after updates.
Diagnosis:
Fix: Use the dynamic version wrapper shown in the Full Reset Procedure above.
TMPDIR Not Set
Claude Code expects TMPDIR to be set to find the socket.
Diagnostic Deep Dive
File Reference
Summary
- Primary issue: Claude.app (Cowork) and Claude Code use different native hosts with incompatible socket formats
- Fix: Disable the native messaging config for whichever one you're NOT using
- After any fix: Must restart Chrome AND Claude Code (MCP connects at startup)
- One profile: Only have Claude extension in one Chrome profile
- One session: Only run one Claude Code instance
Original skill by @jeffzwang from @ExaAILabs. Enhanced and updated for current versions of Claude Desktop and Claude Code.

