fix-chrome-connection

Diagnose and repair broken Claude-in-Chrome MCP connections on macOS.

8|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill fix-chrome-connection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-chrome-connection
Source: https://github.com/MSApps-Mobile/claude-plugins/tree/main/plugins/fix-chrome-connection/skills/fix-chrome-connection
Command: npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill fix-chrome-connection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and repairs broken Claude-in-Chrome MCP connections when tabs_context_mcp fails, the Chrome extension stops responding, sockets become stale, or account switching causes mismatched bridge connections. The Skill walks step-by-step from non-invasive checks (logs, LevelDB account checks, Control_Chrome verification) to targeted fixes (socket symlink repair, AppleScript window creation, reconnection URL, pairing page guidance) and finally guided manual re-auth when required. It also records the steps taken and can commit any new learnings back to the local plugin repository for future runs.

Core Features & Use Cases

  • Structured diagnostics: Run logs + LevelDB checks to classify failure modes (stale socket, auth failure, account mismatch, Chrome not running).
  • Deterministic fixes: Update 0.sock symlink, open pairing pages, run AppleScript to create windows or set URLs, and provide a clear manual re-auth checklist for account switches.
  • Scheduled task awareness: Detect scheduled-session limitations and use Control_Chrome as an alternative health check.
  • Reporting & continuous improvement: Summarize attempted steps, outcomes, and optionally commit self-reflections to the plugin repo.
  • Use case: A user reports "Chrome extension not responding" after switching accounts; run the Skill to identify account mismatch and guide the user through manual re-auth.

Quick Start

Reconnect my Claude Chrome extension, diagnose why tabs_context_mcp fails, and walk me through each repair step.

Frequently Asked Questions about fix-chrome-connection

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

FAQPage Schema
How do I fix a stale socket error in my Claude-in-Chrome MCP connection on macOS?

A stale socket often breaks your Claude-in-Chrome MCP connection. This Skill inspects logs and socket symlinks to classify the failure mode, then updates the 0.sock symlink to restore communication between the Chrome extension and Claude Desktop.

Can I diagnose tabs_context_mcp failures during a scheduled macOS Claude Desktop session?

You can diagnose tabs_context_mcp failures during scheduled macOS Claude Desktop sessions. The Skill detects scheduled-task limitations and uses Control_Chrome as an alternative health check to verify extension responsiveness without standard pairing.

What steps are needed to repair a broken Chrome extension pairing in Claude Desktop?

Repairing a broken Chrome extension pairing involves log inspection, LevelDB account verification, socket symlink updates, and AppleScript window actions. The Skill walks through these steps sequentially and provides pairing-page guidance for final re-authentication.

Does fixing the Claude-in-Chrome connection require manual re-authentication?

Fixing the Claude-in-Chrome connection requires manual re-authentication only when deterministic fixes like socket symlink updates and AppleScript URL actions fail. The Skill provides a clear manual re-auth checklist when automated repairs are insufficient.

When should I not use automated socket symlink repair for my MCP connection?

You should avoid automated socket symlink repair when Chrome is not running or when an account mismatch is the primary cause. The Skill performs non-invasive log and LevelDB checks first to ensure symlink updates target the correct failure mode.