chrome-mcp-troubleshooting
Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.
npx skills add trailofbits/skills --skill chrome-mcp-troubleshooting --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 | Component | Native Host Binary | Socket Location | |-----------|-------------------|-----------------| | **Claude
- When to Use
- When NOT to Use
- The Claude.app vs Claude Code Conflict (Primary Issue)
- Two Native Hosts, Two Socket Formats
- Why They Conflict
- The Fix: Disable Claude.app's Native Host
- Toggle Script
- Quick Diagnosis
- Critical Insight
- Full Reset Procedure (Claude Code CLI)
- Other Common Causes
- Multiple Chrome Profiles
- Multiple Claude Code Sessions
- Hardcoded Version in Wrapper
Disable the Claude.app native messaging config mv ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json \ Ensure the Claude Code config exists and points to the wrapper cat ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json Disable the Claude Code native messaging config mv ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json \ local CONFIG_DIR=~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts local CLAUDE_APP="$CONFIG_DIR/com.anthropic.claude_browser_extension.json" local CLAUDE_CODE="$CONFIG_DIR/com.anthropic.claude_code_browser_extension.json" if [[ -f "$CLAUDE_APP" && ! -f "$CLAUDE_APP.disabled" ]]; then
What does the chrome-mcp-troubleshooting skill do?
Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.
How do I install it?
Run `npx skills add trailofbits/skills --skill chrome-mcp-troubleshooting --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From trailofbits/skills, a repository with 6,426 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.