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.