troubleshooting
Uses Chrome DevTools MCP and documentation to troubleshoot connection
by chromedevtoolsFree
Description
troubleshooting is an agent skill that acts as a step-by-step wizard for fixing a Chrome DevTools MCP setup. It is triggered when list_pages, new_page or navigate_page fails, or when the server will not start. The first step is to find and read the MCP configuration file in your workspace, checking the common locations such as .mcp.json, .vscode/mcp.json and the Gemini and Claude config files. The skill then reads it for common problems, such as incorrect arguments or flags, missing environment variables, and the auto-connect option being used where it does not work. Only if no configuration file can be found does it ask you to paste its contents. The second step is to match the error message against a list of common connection errors before reading the documentation or suggesting changes. The skill is written to give a diagnosis from your actual setup, not a generic checklist. It is published in the chromedevtools/chrome-devtools-mcp repository, which has about 53,600 stars on GitHub. The listing shows it as free, and its security audits show passes from Gen Agent Trust Hub and Socket, with a warning from Snyk.…
Highlights
- Triggered by failed page tools or a server that will not start
- Reads your MCP configuration first
- Checks flags, environment variables and auto-connect
- Matches errors to known connection problems
- Asks for the config only if none is found
Ratings & Reviews
No ratings yet
Be the first to rate troubleshooting.
People also visit
agentmemory-config
Set up and diagnose local agentmemory, including MCP, environment variables
troubleshooting FAQ
When should I use it?
When list_pages, new_page or navigate_page fails, or when the Chrome DevTools MCP server will not start.
What does it check first?
Your MCP configuration file, in locations such as .mcp.json or .vscode/mcp.json, for wrong flags, missing environment variables and auto-connect problems.
Will it ask me for my config?
Only if it cannot find a configuration file in the usual places.
Does it guess at the fix?
No. It matches the error message against known connection errors before it reads the docs or suggests changes.
How do I install it?
Run npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill troubleshooting.
Is it free and checked for security?
The listing shows it as free. Its security audits show passes from Gen Agent Trust Hub and Socket, and a warning from Snyk.
What are the best troubleshooting alternatives?
Popular alternatives to troubleshooting include chrome-devtools, agentmemory-config and browser-testing-with-devtools. See all troubleshooting alternatives