Fix Claude in Chrome MCP connectivity issues
Diagnose the Claude.app-vs-Claude-Code native-host conflict and run the reset procedures — macOS-only troubleshooting for the Claude in Chrome MCP extension
- What
- Diagnose the Claude.app-vs-Claude-Code native-host conflict and run the reset procedures — macOS-only troubleshooting for the Claude in Chrome MCP extension
- Cost
- Free
- Needs
- macOS, Google Chrome, and either Claude Code CLI or the Claude.app (Cowork) — this skill is macOS-only troubleshooting guidance
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the chrome-mcp-troubleshooting skill curated by @trailofbits (original skill by @jeffzwang): use when the Claude in Chrome MCP tools fail with "Browser extension is not connected" or behave erratically. It documents the primary conflict — Claude.app (Cowork) and Claude Code CLI register competing native-messaging hosts with incompatible socket formats — and gives the fix: disable the native-messaging config for whichever one you're NOT using (you can't run both), a chrome-mcp-toggle shell snippet for your ~/.zshrc, a full reset procedure (disable config, rewrite the version wrapper dynamically, kill the native host, clear sockets, restart Chrome, verify the right binary and socket, restart Claude Code), quick-diagnosis commands (which binary, where the socket is, what's connected, which configs are active), and fixes for the other common causes (extension in multiple Chrome profiles, multiple Claude Code sessions, hardcoded version in the wrapper, TMPDIR not set). Honest caveats: macOS only — paths and tools (~/Library/Application Support/, osascript) don't apply to Linux or Windows; the skill runs diagnostic shell commands (ps, lsof, mv on your own Chrome config files, pkill chrome-native-host) that act only on your own local machine — read them before running; not for general Chrome automation issues or network problems. CC-BY-SA-4.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: macOS, Google Chrome, and either Claude Code CLI or the Claude.app (Cowork) — this skill is macOS-only troubleshooting guidance Install "Fix Claude in Chrome MCP connectivity issues" for me. It gives my agent the chrome-mcp-troubleshooting skill: diagnose the Claude.app-vs-Claude-Code native-host conflict, the toggle and full-reset procedures, quick-diagnosis commands, and the other-common-causes fixes — all local to your own machine. CC-BY-SA-4.0 licensed. Repository: https://github.com/trailofbits/skills/blob/main/plugins/claude-in-chrome-troubleshooting/skills/chrome-mcp-troubleshooting/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. This skill legitimately includes local diagnostic shell commands (ps, lsof, mv on Chrome configs, pkill) — they act only on your own machine; confirm that's all they do, then STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "chrome-mcp-troubleshooting". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. pick Claude.app or Claude Code as your one browser-automation driver and disable the other's native host; then restart Chrome). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.