Chrome Mcp Troubleshooting

作者 trailofbits82fe82262526无许可证7.4K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库昨天更新

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.

仅含说明Software Development
AI 生成的概览

诊断并修复 macOS 上 Claude in Chrome MCP 扩展的连接故障，主要是原生主机冲突。

功能
提供针对 macOS 的排查指南，用于处理 Claude in Chrome MCP 浏览器工具无法连接或运行不稳定的问题。它说明了 Claude.app（Cowork）与 Claude Code CLI 原生消息主机之间的冲突及其不兼容的套接字格式，并给出 shell 命令来禁用其中一个配置、运行切换函数、检查进程与套接字以及执行完整重置。还涵盖多个 Chrome 配置文件、多个 Claude Code 会话、包装脚本中硬编码版本以及 TMPDIR 未设置等其他原因。
适用场景
当 mcpclaude-in-chrome* 工具提示浏览器扩展未连接、超时或运行不稳定时使用，尤其是在更新 Claude Code 或 Claude.app 之后，或在 CLI 与桌面应用之间切换时。不适用于 Linux 或 Windows、一般 Chrome 自动化问题、桌面应用问题、网络问题或扩展安装问题。
运行要求
macOS 上的 Chrome 与 Claude 扩展，以及 Claude Code CLI 或 Claude.app；需要 shell 访问权限来运行 ps、lsof、pkill、mv、osascript、getconf 等命令。该技能不附带脚本，命令以说明形式提供。

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

ComponentNative Host BinarySocket Location
Claude.app (Cowork)/Applications/Claude.app/Contents/Helpers/chrome-native-host/tmp/claude-mcp-browser-bridge-$USER/<PID>.sock
Claude Code CLI~/.local/share/claude/versions/<version> --chrome-native-host$TMPDIR/claude-mcp-browser-bridge-$USER (single file)

Why They Conflict

  1. Both register native messaging configs in Chrome:

    • com.anthropic.claude_browser_extension.json → Claude.app helper
    • com.anthropic.claude_code_browser_extension.json → Claude Code wrapper

  2. Chrome extension requests a native host by name

  3. If the wrong config is active, the wrong binary runs

  4. The wrong binary creates sockets in a format/location the MCP client doesn't expect

  5. Result: "Browser extension is not connected" even though everything appears to be running

The Fix: Disable Claude.app's Native Host

If you use Claude Code CLI for browser automation (not Cowork):

bash
# Disable the Claude.app native messaging configmv ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json \   ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json.disabled
# Ensure the Claude Code config exists and points to the wrappercat ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json

If you use Cowork (Claude.app) for browser automation:

bash
# Disable the Claude Code native messaging configmv ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json \   ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json.disabled

You cannot use both simultaneously. Pick one and disable the other.

Toggle Script

Add this to ~/.zshrc or run directly:

bash
chrome-mcp-toggle() {    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        # Currently using Claude.app, switch to Claude Code        mv "$CLAUDE_APP" "$CLAUDE_APP.disabled"        [[ -f "$CLAUDE_CODE.disabled" ]] && mv "$CLAUDE_CODE.disabled" "$CLAUDE_CODE"        echo "Switched to Claude Code CLI"        echo "Restart Chrome and Claude Code to apply"    elif [[ -f "$CLAUDE_CODE" && ! -f "$CLAUDE_CODE.disabled" ]]; then        # Currently using Claude Code, switch to Claude.app        mv "$CLAUDE_CODE" "$CLAUDE_CODE.disabled"        [[ -f "$CLAUDE_APP.disabled" ]] && mv "$CLAUDE_APP.disabled" "$CLAUDE_APP"        echo "Switched to Claude.app (Cowork)"        echo "Restart Chrome to apply"    else        echo "Current state unclear. Check configs:"        ls -la "$CONFIG_DIR"/com.anthropic*.json* 2>/dev/null    fi}

Usage: chrome-mcp-toggle then restart Chrome (and Claude Code if switching to CLI).

Quick Diagnosis

bash
# 1. Which native host binary is running?ps aux | grep chrome-native-host | grep -v grep# Claude.app: /Applications/Claude.app/Contents/Helpers/chrome-native-host# Claude Code: ~/.local/share/claude/versions/X.X.X --chrome-native-host
# 2. Where is the socket?# For Claude Code (single file in TMPDIR):ls -la "$(getconf DARWIN_USER_TEMP_DIR)/claude-mcp-browser-bridge-$USER" 2>&1
# For Claude.app (directory with PID files):ls -la /tmp/claude-mcp-browser-bridge-$USER/ 2>&1
# 3. What's the native host connected to?lsof -U 2>&1 | grep claude-mcp-browser-bridge
# 4. Which configs are active?ls ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic*.json

Critical Insight

MCP connects at startup. If the browser bridge wasn't ready when Claude Code started, the connection will fail for the entire session. The fix is usually: ensure Chrome + extension are running with correct config, THEN restart Claude Code.

Full Reset Procedure (Claude Code CLI)

bash
# 1. Ensure correct config is activemv ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json \   ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json.disabled 2>/dev/null
# 2. Update the wrapper to use latest Claude Code versioncat > ~/.claude/chrome/chrome-native-host << 'EOF'#!/bin/bashLATEST=$(ls -t ~/.local/share/claude/versions/ 2>/dev/null | head -1)exec "$HOME/.local/share/claude/versions/$LATEST" --chrome-native-hostEOFchmod +x ~/.claude/chrome/chrome-native-host
# 3. Kill existing native host and clean socketspkill -f chrome-native-hostrm -rf /tmp/claude-mcp-browser-bridge-$USER/rm -f "$(getconf DARWIN_USER_TEMP_DIR)/claude-mcp-browser-bridge-$USER"
# 4. Restart Chromeosascript -e 'quit app "Google Chrome"' && sleep 2 && open -a "Google Chrome"
# 5. Wait for Chrome, click Claude extension icon
# 6. Verify correct native host is runningps aux | grep chrome-native-host | grep -v grep# Should show: ~/.local/share/claude/versions/X.X.X --chrome-native-host
# 7. Verify socket existsls -la "$(getconf DARWIN_USER_TEMP_DIR)/claude-mcp-browser-bridge-$USER"
# 8. Restart Claude Code

Other Common Causes

Multiple Chrome Profiles

If you have the Claude extension installed in multiple Chrome profiles, each spawns its own native host and socket. This can cause confusion.

Fix: Only enable the Claude extension in ONE Chrome profile.

Multiple Claude Code Sessions

Running multiple Claude Code instances can cause socket conflicts.

Fix: Only run one Claude Code session at a time, or use /mcp to reconnect after closing other sessions.

Hardcoded Version in Wrapper

The wrapper at ~/.claude/chrome/chrome-native-host may have a hardcoded version that becomes stale after updates.

Diagnosis:

bash
cat ~/.claude/chrome/chrome-native-host# Bad: exec "/Users/.../.local/share/claude/versions/2.0.76" --chrome-native-host# Good: Uses $(ls -t ...) to find latest

Fix: Use the dynamic version wrapper shown in the Full Reset Procedure above.

TMPDIR Not Set

Claude Code expects TMPDIR to be set to find the socket.

bash
# Checkecho $TMPDIR# Should show: /var/folders/XX/.../T/
# Fix: Add to ~/.zshrcexport TMPDIR="${TMPDIR:-$(getconf DARWIN_USER_TEMP_DIR)}"

Diagnostic Deep Dive

bash
echo "=== Native Host Binary ==="ps aux | grep chrome-native-host | grep -v grep
echo -e "\n=== Socket (Claude Code location) ==="ls -la "$(getconf DARWIN_USER_TEMP_DIR)/claude-mcp-browser-bridge-$USER" 2>&1
echo -e "\n=== Socket (Claude.app location) ==="ls -la /tmp/claude-mcp-browser-bridge-$USER/ 2>&1
echo -e "\n=== Native Host Open Files ==="pgrep -f chrome-native-host | xargs -I {} lsof -p {} 2>/dev/null | grep -E "(sock|claude-mcp)"
echo -e "\n=== Active Native Messaging Configs ==="ls ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic*.json 2>/dev/null
echo -e "\n=== Custom Wrapper Contents ==="cat ~/.claude/chrome/chrome-native-host 2>/dev/null || echo "No custom wrapper"
echo -e "\n=== TMPDIR ==="echo "TMPDIR=$TMPDIR"echo "Expected: $(getconf DARWIN_USER_TEMP_DIR)"

File Reference

FilePurpose
~/.claude/chrome/chrome-native-hostCustom wrapper script for Claude Code
/Applications/Claude.app/Contents/Helpers/chrome-native-hostClaude.app (Cowork) native host
~/.local/share/claude/versions/<version>Claude Code binary (run with --chrome-native-host)
~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.jsonConfig for Claude.app native host
~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.jsonConfig for Claude Code native host
$TMPDIR/claude-mcp-browser-bridge-$USERSocket file (Claude Code)
/tmp/claude-mcp-browser-bridge-$USER/<PID>.sockSocket files (Claude.app)

Summary

  1. Primary issue: Claude.app (Cowork) and Claude Code use different native hosts with incompatible socket formats
  2. Fix: Disable the native messaging config for whichever one you're NOT using
  3. After any fix: Must restart Chrome AND Claude Code (MCP connects at startup)
  4. One profile: Only have Claude extension in one Chrome profile
  5. One session: Only run one Claude Code instance

Original skill by @jeffzwang from @ExaAILabs. Enhanced and updated for current versions of Claude Desktop and Claude Code.

来源与署名

来源：trailofbits/skills位于plugins/claude-in-chrome-troubleshooting/skills/chrome-mcp-troubleshooting提交82fe822

许可证： 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 trailofbits/skills 的技能

Vector Forge

trailofbits

通过变异测试实现来发现未覆盖代码路径，从而生成密码学测试向量。

Software Development7.4K昨天更新

Wycheproof

trailofbits

指导使用 Project Wycheproof 测试向量验证密码学实现，覆盖已知攻击与边界情况。

Security7.4K昨天更新

Ruzzy

trailofbits

指导安装和使用 Ruzzy——Trail of Bits 面向 Ruby 代码与 C 扩展的覆盖率引导模糊测试器。

Security7.4K昨天更新

Ossfuzz

trailofbits

指导将开源项目接入 OSS-Fuzz，并通过 helper.py 在本地运行模糊测试 harness。

Security7.4K昨天更新

Libfuzzer

trailofbits

指导在 C/C++ 代码上搭建并运行 libFuzzer，涵盖测试框架、构建、语料库、sanitizer 与问题分类。

Software Development7.4K昨天更新

Trailmark

trailofbits

构建并查询多语言源码与二进制代码图，用于安全分析和审计优先级排序。

Security7.4K昨天更新

更多Software Development技能

Playground

anthropics

精选

构建自包含的交互式 HTML 演练场，包含控件、实时预览和可复制的提示词输出。

Software Development37K今天更新

M5 Onboard

anthropics

精选

通过 USB 检测 M5Stack ESP32 开发板，刷写 UIFlow 2.0 固件并安装 MicroPython 应用包。

Software Development37K今天更新

Cardputer Buddy

anthropics

精选

指导迭代 Cardputer-Adv 的 MicroPython 应用包：添加应用、通过 USB 串口推送文件、查看日志并运行 REPL 命令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精选

依据从远程来源获取的 Web Interface Guidelines 审查 UI 代码，并以 file:line 形式报告问题。

Software Development32K5周前更新

Vercel React Native Skills

vercel-labs

精选

React Native 与 Expo 最佳实践规则，涵盖列表性能、动画、导航、UI 模式、状态与 monorepo 配置。

Software Development32K5周前更新

Vercel React Best Practices

vercel-labs

精选

Vercel 的 React 与 Next.js 性能指南，以 70 条规则的形式用于编写、审查和重构代码。

Software Development32K5周前更新