Chrome DevTools Troubleshooting
Diagnoses and resolves connection, configuration, and environment issues for the Chrome DevTools MCP server.
This skill acts as a comprehensive diagnostic wizard designed to identify and fix failures within the Chrome DevTools Model Context Protocol (MCP) environment. It provides a structured step-by-step process to handle common errors such as missing DevToolsActivePort files, configuration typos, and restricted tool availability caused by read-only modes. By automatically searching for configuration files, analyzing error logs, and consulting official documentation, it helps users restore the connection between Claude and the Chrome browser across various operating systems including macOS, Linux, and WSL.
Características Principales
01Diagnostic steps for read-only mode and tool permission issues
02Automated configuration file discovery and analysis
03Detailed guidance for enabling remote debugging and sandboxing fixes
04Pattern-based triage for common connection and port errors
050 GitHub stars
06Integration with official troubleshooting documentation and GitHub issues
Casos de Uso
01Debugging environment-specific connection failures in WSL or sandboxed containers
02Resolving 'Could not find DevToolsActivePort' errors during browser startup
03Fixing tool access issues when the server starts but commands fail