What problem does it solve? When the Chrome DevTools MCP server fails to start, cannot connect to a running Chrome instance, or tools like list_pages, new_page, and navigate_page return errors, this Skill walks you through a structured diagnostic process to identify and fix the root cause. ## Core Features & Use Cases - Configuration Analysis: Locates and reads MCP configuration files (.mcp.json, .claude/settings.json, .vscode/launch.json) to detect incorrect flags, missing environment variables, or incompatible options like --autoConnect. - Error Triage: Maps common errors such as "Could not find DevToolsActivePort", "Target closed", and read-only mode tool restrictions to specific remediation steps. - Guided Verification: Uses list_pages as a safe verification step and runs diagnostic commands like npx chrome-devtools-mcp@latest --help with debug logging. - Use Case: Your MCP client shows only 9 tools instead of the full set. The Skill identifies that read-only mode is enabled in your client and explains how to disable it to unlock browser-modifying tools. ## Quick Start Troubleshoot why my Chrome DevTools MCP server fails with the error "Could not find DevToolsActivePort" when calling list_pages.