troubleshooting

Diagnose and fix Chrome DevTools MCP server connection and configuration failures.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill troubleshooting-pgooone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshooting
Source: https://github.com/Pgooone/oh-pgone-claudecode/tree/main/.claude/plugins/cache/chrome-devtools-plugins/chrome-devtools-mcp/0.20.3/skills/troubleshooting
Command: npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill troubleshooting-pgooone

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix the "Could not find DevToolsActivePort" error in chrome-devtools-mcp?▼

This error means the --autoConnect feature cannot find a running debuggable Chrome instance. Confirm the correct Chrome version is running, then open chrome://inspect/#remote-debugging and enable remote debugging. Afterward, call list_pages to verify the connection.

Why does chrome-devtools-mcp only show 9 tools?▼

A limited tool set indicates your MCP client is enforcing read-only mode, which hides tools annotated with readOnlyHint: false such as click, emulate, and navigate_page. Disable read-only mode in your client, for example by exiting Plan Mode in Gemini CLI.

Should I use --autoConnect or --browserUrl with chrome-devtools-mcp?▼

Use --autoConnect when a debuggable Chrome 144+ instance is already running locally. In sandboxed environments like Claude Desktop or containers, use --browserUrl=http://127.0.0.1:9222 instead, since sandboxing blocks the autoConnect handshake.

Why does chrome-devtools-mcp create a new empty profile instead of connecting?▼

This usually indicates a typo in the server arguments, such as --autoBronnect instead of --autoConnect. Check your MCP configuration file and verify the flags match the documented options exactly.

How do I capture debug logs from chrome-devtools-mcp?▼

Add --logFile with an absolute path to your server arguments, or run DEBUG=* npx chrome-devtools-mcp@latest --logFile=/tmp/cdm-test.log directly. The verbose output helps identify protocol errors, timeouts, and module loading failures.