troubleshooting

Diagnose Chrome DevTools MCP server connection and target failures.

Updated Feb 8, 2023
One-click install
npx skills add https://github.com/mvellandi/winky --skill troubleshooting-mvellandi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting
Source: https://github.com/mvellandi/winky/tree/main/.agents/skills/troubleshooting
Command: npx skills add https://github.com/mvellandi/winky --skill troubleshooting-mvellandi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose and fix Chrome DevTools MCP server connection and target issues when list_pages, new_page, or navigate_page fail, or when the MCP server won't start.

Core Features & Use Cases

  • Provides a structured diagnostic workflow to locate misconfigurations, missing environment variables, and incompatible MCP arguments.
  • Guides verification steps for remote debugging, MCP settings, and known issues with Chrome DevTools MCP.
  • Outlines a full end-to-end troubleshooting path from config discovery to applying fixes and re-running commands.

Quick Start

Start by locating your MCP configuration file and run the troubleshooting wizard to diagnose and fix the Chrome DevTools MCP server setup.

Frequently Asked Questions about troubleshooting

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

FAQPage Schema
Why does my MCP server fail to start when connecting to Chrome DevTools?

The MCP server fails to start due to misconfigurations, missing environment variables, or incompatible MCP arguments. Use a structured diagnostic workflow to locate these setup issues and verify remote debugging in Chrome to restore server initialization.

How do I troubleshoot list_pages, new_page, or navigate_page failures in Chrome DevTools?

To troubleshoot target operation failures for list_pages, new_page, or navigate_page, you must verify your MCP configuration file and apply steps to confirm remote debugging is enabled in Chrome. Following the full end-to-end diagnostic path resolves these command failures.

What is the best way to diagnose Chrome DevTools MCP connection issues?

The best way to diagnose MCP connection issues is to run a troubleshooting wizard that guides you through config discovery, verifies MCP settings, identifies missing environment variables, and applies fixes before re-running your commands.

How do I verify remote debugging in Chrome for an MCP server setup?

To verify remote debugging, locate your MCP configuration file and follow diagnostic steps to check for incompatible MCP arguments and known Chrome DevTools MCP issues. This verification process ensures the server connects properly to Chrome targets.

Can I fix missing environment variables that block MCP server initialization?

Yes, you can fix missing environment variables by discovering your MCP configuration file and running the diagnostic workflow. It locates misconfigurations and missing variables, allowing you to apply the necessary fixes and re-run the server initialization successfully.