chrome-health-check

Probe the Claude Chrome MCP connection and diagnose account mismatches.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly verifies whether the Claude Desktop App and the Chrome extension have an active MCP connection and diagnoses why browser-based automation may fail. It helps avoid wasted time by detecting account mismatches, expired tokens, disabled extensions, or bridge WebSocket issues before running automation tasks.

Core Features & Use Cases

  • Connection probe: Runs a tabs_context_mcp check to confirm connectivity and recognizes the "No Chrome extension connected after discovery" failure mode.
  • Account mismatch diagnosis: Guides extraction and comparison of Desktop App and extension account UUIDs/emails to identify the most common root cause.
  • Remediation steps: Provides step-by-step fixes including logging out and reauthenticating the extension, switching browser Claude.ai sessions via magic link, and restarting the Desktop App and browser to reset discovery.
  • Use Case: Use this Skill before launching Chrome automation pipelines or when a user reports that browser tools are unresponsive.

Quick Start

Run a rapid connectivity check and follow the guided fix steps if the Chrome extension is not connected.

Frequently Asked Questions about chrome-health-check

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

FAQPage Schema
Why is my Claude Chrome extension not connecting to the Desktop App?

Check the Claude Chrome MCP connection by running a tabs_context_mcp probe to verify if Chrome is reachable. This probe detects discovery errors and confirms whether the browser is ready for automation tasks.

How do I diagnose a Claude Chrome MCP connection failure?

Diagnose a Claude Chrome MCP connection failure by extracting and comparing the Desktop App and extension account UUIDs and emails. This account mismatch diagnosis identifies the most common root cause of browser automation pairing issues.

What steps fix the No Chrome extension connected after discovery error?

Fix the No Chrome extension connected after discovery error by logging out and reauthenticating the extension, switching browser Claude.ai sessions via magic link, and restarting the Desktop App and browser to reset discovery.

When should I run a Chrome Claude connection health check?

Run a Chrome Claude connection health check before launching Chrome automation pipelines or when browser tools are unresponsive. It verifies active MCP connectivity and avoids wasted time detecting disabled extensions or expired tokens before running tasks.

Does the Claude bridge WebSocket support troubleshooting expired tokens?

Yes, the Claude bridge WebSocket supports troubleshooting expired tokens by probing the tabs_context_mcp connection. It recognizes the No Chrome extension connected failure mode and prescribes reauthentication remediation steps to restore connectivity.