claude-in-chrome-troubleshooting

Diagnose and fix Chrome MCP extension connectivity by reconfiguring native hosts.

Updated Jul 10, 2025
One-click install
npx skills add https://github.com/Superlend/superloop-core-contracts --skill claude-in-chrome-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-in-chrome-troubleshooting
Source: https://github.com/Superlend/superloop-core-contracts/tree/main/.cursor/skills/claude-in-chrome-troubleshooting/skills/claude-in-chrome-troubleshooting
Command: npx skills add https://github.com/Superlend/superloop-core-contracts --skill claude-in-chrome-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers quickly diagnose and fix connectivity issues between Claude in Chrome MCP extension and its native host, particularly when the extension reports "Browser extension is not connected" or behaves erratically.

Core Features & Use Cases

  • Connection diagnostics: Identify which native host is active and which sockets are in use.
  • Configuration remediation: Disable the conflicting native host config and enable the correct one for Claude Code CLI or Claude.app Cowork.
  • Recovery workflow: Restart Chrome and Claude software to re-establish MCP connections after changes.

Quick Start

  1. Check for the active native host process and socket locations.
  2. Disable the non-used native host by moving its JSON config out of the Chrome NativeMessagingHosts directory, then enable the desired one.
  3. Quit and relaunch Google Chrome, then restart Claude Code CLI or Claude.app as appropriate.

Frequently Asked Questions about claude-in-chrome-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix the Claude MCP Chrome extension when it says Browser extension is not connected?

To fix the Claude MCP Chrome extension connection error, you must identify the active native host, disable conflicting native messaging configs, and restart Chrome and Claude software to re-establish the MCP connection.

Why does my Claude in Chrome MCP extension behave erratically after using Claude Code CLI?

The Claude in Chrome MCP extension behaves erratically due to conflicting native hosts and sockets. Switching between Claude Code CLI and Claude.app Cowork requires toggling the correct Chrome native messaging config to resolve the conflict.

How do I check which native host is active for the Claude MCP extension?

To check which native host is active for the Claude MCP extension, run connection diagnostics to identify the active native host process and verify which socket locations are currently in use.

How do I disable a conflicting native host config for Claude in Chrome?

To disable a conflicting native host config for Claude in Chrome, move the unused JSON config file out of the Chrome NativeMessagingHosts directory, then enable the desired config for your specific Claude tool.

What is the restart sequence to restore a working MCP connection in Chrome?

The restart sequence to restore an MCP connection requires quitting and relaunching Google Chrome, followed by restarting the Claude Code CLI or Claude.app Cowork software to re-establish connectivity.