troubleshooting

Diagnose and fix Chrome DevTools MCP server connection and target issues.

2|Updated Mar 26, 2026

Search Tags:#debugging #troubleshooting #configuration #diagnostics #server-setup #chrome-devtools-mcp

Ready to run

npx skills add https://github.com/calvingit/skills --skill troubleshooting-calvingit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: troubleshooting
Source: https://github.com/calvingit/skills/tree/main/external-skills/Tool/troubleshooting
Command: npx skills add https://github.com/calvingit/skills --skill troubleshooting-calvingit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose and fix Chrome DevTools MCP server connection and target issues when typical commands fail or the server cannot start.

Core Features & Use Cases

Locate and read MCP configuration files (.mcp.json, gemini-extension.json, .claude/settings.json, .vscode/launch.json, or .gemini/settings.json) to identify misconfigurations.
Triage common connection errors such as Could not find DevToolsActivePort and guide users through enabling remote debugging and verifying Chrome is running.
Read known issues documentation and propose recommended configuration changes, including whether to use --browserUrl or enable remote debugging prompts.
Provide step-by-step diagnostic guidance, run commands like list_pages to verify connections, and document actionable fixes for downstream tooling.
Create a suggested MCP client configuration snippet and outline when to adjust startup_timeout_ms or log files.

Quick Start

Follow the wizard to diagnose and fix an MCP server connection issue.

Frequently Asked Questions about troubleshooting

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

FAQPage Schema

Why does my Chrome DevTools MCP server fail with Could not find DevToolsActivePort?▼

The Could not find DevToolsActivePort error means Chrome lacks remote debugging enabled. You must launch Chrome with the --remote-debugging-port flag and verify the process is actively running before initializing the MCP server connection.

How do I fix Chrome DevTools MCP connection issues when list_pages or navigate_page fail?▼

To fix Chrome DevTools MCP connection failures, locate and read your MCP configuration files such as .mcp.json or .vscode/launch.json to identify misconfigurations. Then triage common errors and apply recommended configuration changes.

Does the Chrome DevTools MCP server work in CI environments?▼

Yes, the Chrome DevTools MCP server works in CI environments. Diagnostic guidance covers both local and CI contexts, helping you verify connections by running commands like list_pages and adjusting startup_timeout_ms to prevent initialization timeouts.

What is the best way to configure Chrome DevTools MCP using --browserUrl?▼

The best way to configure --browserUrl is to consult known issues documentation and apply the suggested MCP client configuration snippet. This provides concrete configuration changes to resolve server initialization and target connection issues.

When should I adjust startup_timeout_ms for MCP server configuration?▼

You should adjust startup_timeout_ms when MCP server initialization errors occur due to slow Chrome startup. The diagnostic wizard outlines when to modify this timeout and helps outline log file configurations to capture failure details.