Troubleshooting
When Chrome DevTools MCP connections fail, this skill walks you through the diagnostic process systematically. It starts by hunting down your config files, then triages common errors like "Could not find DevToolsActivePort" with specific fix sequences. The approach is methodical: confirm Chrome is running, verify remote debugging is enabled at chrome://inspect, then test with list_pages before anything fancy. It knows the difference between a typo in autoConnect and actual sandboxing issues, catches when you're stuck in read-only mode with only 9 tools available, and will check the troubleshooting docs or GitHub issues if needed. Basically a runbook that stops you from randomly tweaking flags when your browser automation breaks.
- skills.sh installs
- 3.5K
- GitHub stars
- 55K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add chromedevtools/chrome-devtools-mcp --skill troubleshooting --agent claude-codeInstalls into .claude/skills of the current project.
Files
Troubleshooting Wizard
You are acting as a troubleshooting wizard to help the user configure and fix their Chrome DevTools MCP server setup. When this skill is triggered (e.g., because list_pages, new_page, or navigate_page failed, or the server wouldn't start), follow this step-by-step diagnostic process:
Step 1: Find and Read Configuration
Your first action should be to locate and read the MCP configuration file. Search for the following files in the user's workspace: .mcp.json, .vscode/mcp.json, gemini-extension.json, or .gemini/settings.json (or user-scoped files such as ~/.claude.json if accessible).
If you find a configuration file, read and interpret it to identify potential issues such as:
- Incorrect arguments or flags.
- Missing environment variables.
- Usage of
--autoConnectin incompatible environments.
If you cannot find any of these files, only then should you ask the user to provide their configuration file content.
Step 2: Triage Common Connection Errors
Before reading documentation or suggesting configuration changes, check if the error message matches one of the following common patterns.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageDetails
- Repository
- github.com/chromedevtools/chrome-devtools-mcp
- Categories
- Backend & APIs, Documentation, AI & Agent Building, Debugging
- First seen
- May 16, 2026
More from chromedevtools/chrome-devtools-mcp
All 6Recommended
More Backend & APIs
signal-postmortemtradermonty/claude-trading-skillsRecord and analyze post-trade outcomes for signals generated by edge pipeline and other skills. Track false positives, missed opportunities, and regime mismatch3.5Kskills.sh installs
semanticscholar-skillagents365-ai/365-skillsUse when searching academic papers, looking up citations, finding authors, or getting paper recommendations using the Semantic Scholar API. Triggers on queries 3.5Kskills.sh installs
chatgpt-appsopenai/skillsBuild, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, regist3.5Kskills.sh installs
file-conversionwshobson/agentsConvert files between formats — PDF to Word, HEIC to JPG, MP4 to MP3, CSV to JSON, EPUB to MOBI, and 999 total routes across images, video, audio, documents, da3.4Kskills.sh installstrade-hypothesis-ideatortradermonty/claude-trading-skillsGenerate falsifiable trade strategy hypotheses from market data, trade logs, and journal snippets. Use when you have a structured input bundle and want ranked h3.4Kskills.sh installs
graphvizmarkdown-viewer/skillsCreate directed/undirected graphs using DOT language with automatic layout. Best for dependency trees, call graphs, package hierarchies, and module relationship3.4Kskills.sh installs