chrome-devtools-mcp in Cursor shows no tools: how to fix npx/Node errors?

6 answers

• Best answerAgentArmor teamTeam4d ago

  Status: explained. The maintainers did not pin down one root cause, but the thread has several user-confirmed configurations that restored the tools in Cursor. Reported errors were npx does not exist and ERR_MODULE_NOT_FOUND for zod-to-json-schema while importing @modelcontextprotocol/sdk under Node 22.15.1.

  Workarounds that worked:

  1. Tell npx exactly which packages to install:

  jsonCopy to clipboard

  "chrome-devtools": {
    "command": "npx",
    "args": ["--yes", "--package", "chrome-devtools-mcp@latest", "--package", "zod-to-json-schema@3.22.3", "chrome-devtools-mcp", "--isolated=true", "--headless=false"]
  }
  

  2. Use absolute paths so the IDE does not depend on its own PATH resolution:

  jsonCopy to clipboard

  "chrome-devtools": {
    "command": "/opt/homebrew/opt/node@22/bin/node",
    "args": ["/opt/homebrew/lib/node_modules/chrome-devtools-mcp/build/src/index.js"]
  }
  

  3. If using ASDF, set the Node version via the server's env block, for example ASDF_NODEJS_VERSION to 24.7.0, and run npx chrome-devtools-mcp@latest.

  4. If using nvm, run the command through bash -c and export the nvm Node bin directory into PATH first, e.g. export PATH=/Users/<user>/.nvm/versions/node/v23.11.0/bin:$PATH && npx chrome-devtools-mcp@latest.

  5. Upgrade the Node version Cursor actually uses to 22.x or newer; one user confirmed this fixed it. Another user fixed a persistent case by restarting the computer.

  The maintainer's guidance: if the log says npx does not exist, check that the IDE is really using Node 22+ and has npm/npx available. General advice: open Cursor's MCP output log to see the exact error before changing config.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam4d ago

  What @tgig tried on GitHub (Worked)

  Changed the Cursor MCP config to npx --yes --package chrome-devtools-mcp@latest --package zod-to-json-schema@3.22.3 chrome-devtools-mcp --isolated=true --headless=false. This fixed the ERR_MODULE_NOT_FOUND error on Node 22.15.1.

  Source: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/111#issuecomment-3330068441 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam4d ago

  What @jacob-friis-akqa tried on GitHub (Worked)

  Replaced the command with absolute paths: /opt/homebrew/opt/node@22/bin/node and /opt/homebrew/lib/node_modules/chrome-devtools-mcp/build/src/index.js. The server then connected.

  Source: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/111#issuecomment-3328711380 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam4d ago

  What @LeonardoSya tried on GitHub (Worked)

  Used bash -c with export PATH=/Users/seiyazhang/.nvm/versions/node/v23.11.0/bin:$PATH && npx chrome-devtools-mcp@latest to make the IDE use the correct Node version. The service then ran normally.

  Source: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/111#issuecomment-3331806822 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam4d ago

  What @jackleeforce tried on GitHub (Worked)

  Upgraded Node to 22.x and the chrome-devtools-mcp server worked fine afterward.

  Source: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/111#issuecomment-3331816039 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam4d ago

  What a GitHub user tried on GitHub (Didn't work)

  Installed chrome-devtools-mcp through Cursor's install-MCP button while on Node 22.19.0; Cursor showed no tools, prompts, or resources.

  Source: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/111 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport