What problem does it solve? When the Chrome DevTools MCP server fails to start, cannot connect to a running Chrome instance, or exposes only a limited set of tools, this Skill walks through a structured diagnostic process to identify the root cause and produce a working configuration. ## Core Features & Use Cases - Configuration Inspection: Locates and reads MCP config files such as .mcp.json, .claude/settings.json, or .vscode/launch.json to detect incorrect flags, missing environment variables, or typos like --autoBronnect. - Error Triage: Maps common errors like "Could not find DevToolsActivePort", "Target closed", and missing tools to specific fixes, including enabling remote debugging at chrome://inspect or disabling read-only mode in the MCP client. - Configuration Generation: Produces corrected MCP server JSON snippets, recommending --browser-url for sandboxed environments, --logFile for debug capture, or increased startup_timeout_ms on Windows. - Use Case: If list_pages fails after setup, the Skill verifies Chrome is running with remote debugging enabled, retries list_pages, and escalates to log analysis or GitHub issue searches only if needed. ## Quick Start Ask the assistant to troubleshoot why the Chrome DevTools MCP server fails when calling list_pages or new_page.
