Problem to locate chrome.exe on windows 64 bits.

[Prestaplugins]

Describe the bug
I'm trying to use chrome-devtools MCP with Cursor on windows 10 64 bits. I spent my full day trying to make it work, but I failed.
The problem is that it never finds chrome.exe, even when I use --executablePath option.

To Reproduce
Use cursor and windows 64 bits.
Add the MCP server using mcp.json like this :

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest",
        "--",
        "--executablePath",
        "C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe"
      ]
    }
  }
}

Try this prompt :
Using chrome-devtools MCP, check LCP for https://web.dev and stop on the 1st error. Show me the error.

Check the result :
"Could not find Google Chrome executable for channel 'stable' at 'C:\Program Files\Google\Chrome\Application\chrome.exe'."

Expected behavior
Use the executablePath option to locate chrome.exe

Chrome version:
140.0.7339.208

[sebastianbenz]

Can you please try escaoping the backlash in the path? "C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe"?

[Prestaplugins]

Yes of course I did, that's github who was removing it ;-)

[sebastianbenz]

Hah, that would've been too easy. Does it work if you launch chrome-devtools mcp from the commandline?

[Prestaplugins]

npx chrome-devtools-mcp@latest -- --executablePath "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"

Give this result :
chrome-devtools-mcp exposes content of the browser instance to the MCP clients allowing them to inspect,
debug, and modify any data in the browser or DevTools.
Avoid sharing sensitive or personal information that you do want to share with MCP clients.

It doesn't launch Chrome.

[OrKoN]

Chrome is launched when the first tool call is being sent. Can you try the alternative format for executablePath:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest",
        "--",
        "--executablePath=C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe"
      ]
    }
  }
}

I was not able to reproduce so far but when testing with the MCP inspector I saw that our server did not receive the correct arg if it contained whitespaces.

[Prestaplugins]

I already tried this too, with or without quote, and even with "--e" parameters.

The result is always the same, it seems ignored and the error is still the following :
Could not find Google Chrome executable for channel 'stable' at 'C:\Program Files\Google\Chrome\Application\chrome.exe'.

I also tried tons of other things, like creating a symbolic link from C:\Program Files\Google\Chrome\Application\chrome.exe to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe.

This time it was different, the error message was : spawn UNKNOWN
Chatgpt advised me to try launching Cursor as an administrator, but nothing changed.

[OrKoN]

I think https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/150/files might help here although I was not quite able to reproduce. I noticed though that we were setting the channel argument to the default value when an executable path was provided.

[OrKoN]

Could you please try with the --executable-path on the latest version that was just released v0.3.0?

[OrKoN]

So we check for the default path by expecting Chrome at this location:${process.env['PROGRAMFILES']}\\Google\\Chrome\\Application\\chrome.exe. Generally, you should not need to use the executable path parameter. But it looks like on your machine the environment variable might not be pointing to Program Files (x86) but to Program Files. Could you please try to set PROGRAMFILES env variable in the MCP server config to the path to Program Files (x86)?