Bug: browser-tools-mcp fails to start on Windows with "command not found" error

[arselanmoney]

Operating System: Windows 11
Problem Description:
The browser-tools-mcp service fails to start when launched by the MCP framework in VS Code. It shows a garbled error message (which seems to be "command not found") and a Connection closed error.

Debugging Steps Taken:

Initial error was ENOENT: ... lstat '...\${APPDATA}'.

This was caused by an incorrect NPM prefix environment. We worked around this by adding "--prefix", "C:\Users\Arselan\AppData\Roaming\npm" to the args in mcpServers.json.

After fixing the prefix, the NPM log showed the process exited with code 1.

Crucially, when I run the exact same command manually in a standard Windows terminal, the program starts successfully without crashing. It enters a "server discovery" mode, which is expected.

Manual Command (Works Successfully):

cd E:\MCP\browser-tools-mcp\browser-tools-mcp
npx --prefix "C:\Users\Arselan\AppData\Roaming\npm" @agentdeskai/browser-tools-mcp@latest
Conclusion:
This proves that the package itself is not broken, but the execution environment provided by the MCP launcher in VS Code is likely incomplete (possibly a missing PATH entry), causing a "command not found" error internally when the script runs.

"github.com/AgentDeskAI/browser-tools-mcp": {
  "command": "npx.cmd",
  "args": [
    "--prefix",
    "C:\\Users\\Arselan\\AppData\\Roaming\\npm",
    "@agentdeskai/browser-tools-mcp@latest"
  ],
  "cwd": "E:\\MCP\\browser-tools-mcp\\browser-tools-mcp",
  "disabled": false,
  "autoApprove": []
},

[pankajjangid]

@arselanmoney Yes with manual it's working fine

{ "mcpServers": { "browser-tools": { "command": "npx.cmd", "args": [ "--prefix", "C:\\Users\\Pankaj\\AppData\\Roaming\\npm", "@agentdeskai/browser-tools-mcp@latest" ], "cwd": "D:\\tools\\github\\browser-tools-mcp-main\\browser-tools-mcp", "disabled": false, "autoApprove": [] } } }