chrome▌

Diagnose and resolve Claude in Chrome MCP extension connectivity conflicts on macOS. \n \n Addresses the primary issue: Claude.app (Cowork) and Claude Code CLI use competing native messaging hosts with incompatible socket formats; fix by disabling one config and restarting both Chrome and Claude Code \n Provides quick diagnosis commands to identify which native host is running, locate socket files, and verify active configurations \n Includes a toggle script to switch between Claude.app and Clau

Lightweight Chrome DevTools Protocol CLI. Connects directly via WebSocket — no Puppeteer, works with 100+ tabs, instant connection.

Chrome DevTools integration for debugging, performance analysis, and browser automation via MCP. \n \n Provides tools for page navigation, element inspection via snapshots, clicking, form filling, screenshot capture, and JavaScript evaluation \n Operates on a persistent Chrome profile with automatic browser startup; switch between multiple pages using list_pages and select_page \n Supports efficient workflows: navigate, wait for content, take snapshots to identify elements by uid , then interact

Skill by ara.so — Daily 2026 Skills collection.

Automate browser tasks in the user's real Chrome session via the agent-browser CLI.

Standalone script: No download; the skill invokes .claude/tools/chrome-browser/chrome-browser.cjs (Node.js v18+ required).