Skip to content
SkillModel-led2,548 tokens in use

Chrome MCP Troubleshooting

Diagnoses and fixes Claude in Chrome MCP connection failures on macOS, including the native host conflict between Claude.app and the Claude Code CLI.

8,319 stars on the repository CC-BY-SA-4.0trailofbits/skills · plugins/chrome-mcp-troubleshooting/skills/chrome-mcp-troubleshooting
/plugin marketplace add trailofbits/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Chrome MCP Troubleshooting costs

48tokens idle
2,548tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure25/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources0/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 54
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 54

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community64
  • Maturity32
  • Momentum40

Chrome MCP Troubleshooting helps when the Claude in Chrome tools fail with “Browser extension is not connected” or behave erratically. Its main finding is that Claude.app (Cowork) and the Claude Code CLI each register their own Chrome native messaging host, and the wrong one can win, so sockets end up where the MCP client does not look.

The skill gives a quick diagnosis with process, socket and config checks, a toggle function that switches between the two hosts, and a full reset procedure. It covers macOS only.

What You Get

  • A quick diagnosis made of ps, ls and lsof checks for the native host, its socket and active configs
  • A chrome-mcp-toggle shell function that switches between Claude Code CLI and Claude.app
  • A full reset procedure for the CLI path, ending with restarting Chrome and Claude Code
  • A file reference and a diagnostic deep dive for stubborn cases

Common Use Cases

  • Browser automation tools return Browser extension is not connected
  • Chrome tools stop working after updating Claude Code or Claude.app
  • Switching between the Claude Code CLI and Cowork for browser automation
  • The native host process is running but MCP calls still time out

What Makes It Unique

Generic Chrome automation advice does not cover this problem. The skill names the two competing native hosts, their different socket formats and the exact config files to rename, and it says that only one of them can be active at a time. It is limited to macOS and lists when not to use it.

Under The Hood

The skill is a single instruction file. When followed, the agent runs shell commands on your Mac: it lists processes and sockets, renames files in the Chrome NativeMessagingHosts folder, and in the reset procedure stops the native host process and deletes the socket files in the temp folder. It also suggests adding a function to your shell profile and editing a wrapper script. It does not fetch web pages or call remote APIs. Because it changes configuration files and kills a process, check each command before it runs.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers