File tree Expand file tree Collapse file tree 1 file changed +24
-0
lines changed
Expand file tree Collapse file tree 1 file changed +24
-0
lines changed Original file line number Diff line number Diff line change 1+ # Troubleshooting
2+
3+ ## General tips
4+
5+ - Run ` npx chrome-devtools-mcp@latest --help ` to test if the MCP server runs on your machine.
6+ - Make sure that your MCP client has the same npm and node versions.
7+ - When configuring your MCP client, try using the ` --yes ` argument to ` npx ` to
8+ auto-accept installation prompt.
9+ - Find a specific error in the output of the ` chrome-devtools-mcp ` server.
10+ Usually, if you client is an IDE, logs would be in the Output pane.
11+
12+ ## Specific problems
13+
14+ ### ` Error [ERR_MODULE_NOT_FOUND]: Cannot find module ... `
15+
16+ This usually indicates either a non-supported Node version is in use or that the
17+ ` npm ` /` npx ` cache is corrupted. Try clearing the cache, unsintalling
18+ ` chrome-devtools-mcp ` and installing it again.
19+
20+ ### ` Target closed ` error
21+
22+ This indicates that the browser could not be started. Make sure that no Chrome
23+ instances are running or close them. Make sure you have the latest stable Chrome
24+ installed and that [ your system is able to run Chrome] .
You can’t perform that action at this time.
0 commit comments