chromedevtools--chrome-devtools-mcp
Alex Rudenko
a9fc8636fc
starting a doc with troubleshooting tips --------- Co-authored-by: Sebastian Benz <sbenz@google.com>
30 行
1.2 KiB
Markdown
30 行
1.2 KiB
Markdown
# Troubleshooting
|
|
|
|
## General tips
|
|
|
|
- Run `npx chrome-devtools-mcp@latest --help` to test if the MCP server runs on your machine.
|
|
- Make sure that your MCP client uses the same npm and node version as your terminal.
|
|
- When configuring your MCP client, try using the `--yes` argument to `npx` to
|
|
auto-accept installation prompt.
|
|
- Find a specific error in the output of the `chrome-devtools-mcp` server.
|
|
Usually, if you client is an IDE, logs would be in the Output pane.
|
|
|
|
## Specific problems
|
|
|
|
### `Error [ERR_MODULE_NOT_FOUND]: Cannot find module ...`
|
|
|
|
This usually indicates either a non-supported Node version is in use or that the
|
|
`npm`/`npx` cache is corrupted. Try clearing the cache, uninstalling
|
|
`chrome-devtools-mcp` and installing it again. Clear the cache by running:
|
|
|
|
```sh
|
|
rm -rf ~/.npm/_npx # NOTE: this might remove other installed npx executables.
|
|
npm cache clean --force
|
|
```
|
|
|
|
### `Target closed` error
|
|
|
|
This indicates that the browser could not be started. Make sure that no Chrome
|
|
instances are running or close them. Make sure you have the latest stable Chrome
|
|
installed and that [your system is able to run Chrome](https://support.google.com/chrome/a/answer/7100626?hl=en).
|