chrome-devtools-mcp shows "No tools" in Cursor although the same command works in the terminal

6 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Closed as a duplicate; the maintainer explained the likely cause: chrome-devtools-mcp requires Node 22.12.0+ and Cursor must be configured to use the same Node version as your terminal. In this thread the reporter's terminal had Node v22.13.0, but Cursor's "About Cursor" page showed Node 20.19.1, so upgrading the system Node alone wasn't enough. No crash or server error was reported; Cursor just listed zero tools.

  The fix that worked for several commenters was pointing Cursor at the absolute path of your Node npx binary and setting PATH in the server env:

  jsonCopy to clipboard

  {
    "mcpServers": {
      "chrome-devtools": {
        "command": "/Users/YOUR_USERNAME/.nvm/versions/node/v22.18.0/bin/npx",
        "args": ["chrome-devtools-mcp@latest", "--channel=dev"],
        "env": {
          "PATH": "/Users/YOUR_USERNAME/.nvm/versions/node/v22.18.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin",
          "SHELL": "/bin/zsh"
        }
      }
    }
  }
  

  One commenter also deleted Cursor's MCP npm cache and confirmed npx then worked:

  bashCopy to clipboard

  rm -rf ~/Library/Application\ Support/Cursor/User/workspaceStorage/*/anysphere.cursor-mcp/mcp-npm
  

  Another commenter suggested replacing npx with pnpm ("command": "pnpm dlx", "args": ["chrome-devtools-mcp@latest"]), which fixed npx failing in the terminal for them. General advice: use your own Node install path/version in the JSON and verify the cache path before running rm -rf, then restart Cursor after changing the config.

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

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

  Added the server to Cursor's mcp.json as "command": "npx chrome-devtools-mcp@latest", "args": []. Cursor still showed "No tools, prompts, or resources" and the agent couldn't call the tools.

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

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

  What @NorthSeacoder tried on GitHub (Worked)

  Used the absolute npx path from an nvm Node install (/Users/.../.nvm/versions/node/v22.18.0/bin/npx) with matching PATH in env and --channel=dev, then cleared Cursor's MCP npm cache with rm -rf ~/Library/Application Support/Cursor/User/workspaceStorage/*/anysphere.cursor-mcp/mcp-npm. Comment 8 confirmed npx worked after deleting the cache, and comment 11 said this was the only fix that worked.

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

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

  What @WJ-Yuan tried on GitHub (Didn't work)

  Suggested upgrading Node. The reporter replied that their terminal was already on v22.13.0 while Cursor's About page showed Node 20.19.1, and the issue persisted.

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

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

  What @WJ-Yuan tried on GitHub (Outcome unclear)

  Switched from npx to pnpm dlx ("command": "pnpm dlx", "args": ["chrome-devtools-mcp@latest"]) on Node v22.14.0 / pnpm 10.10.0, which fixed npx failing in the terminal; whether it fixed Cursor wasn't confirmed in the thread.

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

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

  What @bansavage tried on GitHub (Outcome unclear)

  For nvm users: nvm install 22.12.0, set it as the default alias, add a repo .nvmrc with 22.12.0, and restart Cursor. Posted as a step-by-step guide; not explicitly confirmed in later comments.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport