Troubleshooting
Skill Verified ActiveUses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
To help users effectively troubleshoot and resolve connection and target issues with Chrome DevTools MCP server configurations, ensuring reliable browser automation and debugging.
Features
- Step-by-step diagnostic process for MCP issues
- Identification of common error patterns and their specific causes
- Guidance on enabling remote debugging and checking Chrome versions
- Troubleshooting for missing tools and extension loading failures
- Reference to known issues and documentation for advanced problems
Use Cases
- When `list_pages`, `new_page`, or `navigate_page` fail in an MCP setup.
- When the Chrome DevTools MCP server fails to initialize or start.
- When encountering 'Could not find DevToolsActivePort' errors with `--autoConnect`.
- When only a limited set of MCP tools are available, indicating read-only mode.
Non-Goals
- Performing MCP server configuration or modification.
- Directly controlling the Chrome browser.
- Providing general Chrome browser troubleshooting unrelated to MCP.
Installation
First, add the marketplace
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp/plugin install chrome-devtools-mcp@chrome-devtools-pluginsQuality Score
VerifiedTrust Signals
Similar Extensions
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
X Twitter Scraper
100Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes
Root Cause Tracing
99Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior