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.