cursor remote can not link to the chrome at win

[jaffe-fly]

Describe the bug

"chrome-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest",
        "--browserUrl=http://192.168.x.xxx:9222"
      ]

installed the MCP in cursor remote, http://192.168.x.xxx:9222 is chrome instance at win.

when input Check the performance of https://developers.chrome.com

some logs

2025-09-25 14:04:53.349 [info] Successfully connected to stdio server
2025-09-25 14:04:53.349 [info] Storing stdio client user-chrome-devtools
2025-09-25 14:04:53.349 [info] CreateClient completed, server stored: true
2025-09-25 14:04:53.432 [info] Handling ListOfferings action, server stored: true
2025-09-25 14:04:53.432 [info] Connected to stdio server, fetching offerings
2025-09-25 14:04:53.443 [info] Found 26 tools and 0 prompts
2025-09-25 14:12:20.202 [info] Handling CallTool action for tool 'list_pages'
2025-09-25 14:12:20.202 [info] Calling tool 'list_pages' with toolCallId: tool_24d8ac3d-25c5-48dc-9fbd-75842ea7e7b
2025-09-25 14:12:20.212 [info] Successfully called tool 'list_pages'
2025-09-25 14:13:45.411 [info] Handling DeleteClient action
2025-09-25 14:13:45.411 [info] Cleaning up
2025-09-25 14:13:45.411 [info] Handling DeleteClient action
2025-09-25 14:13:45.475 [info] Handling CreateClient action
2025-09-25 14:13:45.475 [info] Starting new stdio process with command: npx chrome-devtools-mcp@latest --browserUrl=http://192.168.x.xxx:9222
2025-09-25 14:13:45.475 [info] Handling CreateClient action
2025-09-25 14:13:45.475 [info] Starting new stdio process with command: npx chrome-devtools-mcp@latest --browserUrl=http://192.168.x.xxx:9222
2025-09-25 14:13:45.527 [info] Handling ListOfferings action, server stored: false
2025-09-25 14:13:45.527 [error] No server info found
2025-09-25 14:13:45.527 [info] Handling ListOfferings action, server stored: false
2025-09-25 14:13:45.527 [error] No server info found
2025-09-25 14:13:45.573 [info] Handling ListOfferings action, server stored: false
2025-09-25 14:13:45.573 [error] No server info found
2025-09-25 14:13:45.573 [info] Handling ListOfferings action, server stored: false
2025-09-25 14:13:45.573 [error] No server info found
2025-09-25 14:13:46.740 [error] 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.

2025-09-25 14:13:46.743 [error] 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.

2025-09-25 14:13:46.746 [info] Successfully connected to stdio server
2025-09-25 14:13:46.746 [info] Storing stdio client user-chrome-devtools
2025-09-25 14:13:46.746 [info] CreateClient completed, server stored: true
2025-09-25 14:13:46.748 [info] Successfully connected to stdio server
2025-09-25 14:13:46.749 [info] A second client was created while connecting, discarding it.
2025-09-25 14:13:46.749 [info] CreateClient completed, server stored: true
2025-09-25 14:13:46.765 [info] Handling ListOfferings action, server stored: true
2025-09-25 14:13:46.765 [info] Handling ListOfferings action, server stored: true
2025-09-25 14:13:46.765 [info] Connected to stdio server, fetching offerings
2025-09-25 14:13:46.765 [info] Connected to stdio server, fetching offerings
2025-09-25 14:13:46.768 [info] Handling ListOfferings action, server stored: true
2025-09-25 14:13:46.768 [info] Connected to stdio server, fetching offerings
2025-09-25 14:13:46.770 [info] Handling ListOfferings action, server stored: true
2025-09-25 14:13:46.770 [info] Connected to stdio server, fetching offerings
2025-09-25 14:13:46.773 [info] Found 26 tools and 0 prompts
2025-09-25 14:13:46.779 [info] Found 26 tools and 0 prompts
2025-09-25 14:13:46.779 [info] Found 26 tools and 0 prompts
2025-09-25 14:13:46.779 [info] Found 26 tools and 0 prompts
2025-09-25 14:14:06.352 [info] Handling CallTool action for tool 'list_pages'
2025-09-25 14:14:06.352 [info] Calling tool 'list_pages' with toolCallId: tool_984d6720-8d32-4cb6-8f9d-d5356155838
2025-09-25 14:14:06.379 [info] Successfully called tool 'list_pages'
2025-09-25 14:14:13.234 [info] Handling CallTool action for tool 'new_page'
2025-09-25 14:14:13.234 [info] Calling tool 'new_page' with toolCallId: tool_c9c6548d-cd67-4137-a2d5-1233e6d2c07
2025-09-25 14:14:13.240 [info] Successfully called tool 'new_page'

Chrome version:

Coding agent version: cursor 1.5.5

[OrKoN]

Hi, thanks for reporting! http://192.168.x.xxx:9222 needs to be be accessible to the client but it appears that it is not. Note that Chrome listens on the localhost and not on the external interface so usually Chrome needs to run on the same machine as client and you should use http://127.0.0.1:9222 to access it (unless you set up port forwarding on the machine with Chrome to send external traffic to localhost). Let me know if it was helpful!

[mehrazi]

Hi @OrKoN,
I attempted to do the same. Both my cursor and Chrome are running on a remote server. However, I’m unable to use the MCP.

MCP config:

{ "mcpServers": { "chrome-devtools": { "command": "npx", "args": [ "chrome-devtools-mcp@latest", "--headless=true", "--browserUrl=http://127.0.0.1:9222", "--logFile /tmp/chrome-devtools-mcp-log.txt" ] } } }
chrome command:

$ google-chrome --headless --remote-debugging-address=127.0.0.1 --remote-debugging-port=9222 --no-sandbox --disable-gpu

node v22.20.0 (npm v10.9.3)

[OrKoN]

Chrome does not allow starting the remote debugging on the default user data dir so you would need to provide a custom one via --user-data-dir. See https://developer.chrome.com/blog/remote-debugging-port for more details. Let me know if that worked. Also, please check that Cursor is actually using the correct node version. Sometimes Cursor seems to use a different node version and not the one in the terminal if multiple versions are installed.

[mehrazi]

Thanks, @OrKoN. Based on your guidance, I do these:

new chrome command:
...@ubuntu..:~/.../...$ mkdir -p ~/chrome-remote-debug ...@ubuntu...:~/.../...$ google-chrome \ --remote-debugging-address=127.0.0.1 \ --remote-debugging-port=9222 \ --user-data-dir=~/chrome-remote-debug \ --no-sandbox \ --disable-gpu \ --headless

node version check code:
// node-version-check.js console.log('Node.js version:', process.version); console.log('Node.js executable path:', process.execPath); console.log('Platform:', process.platform); console.log('Architecture:', process.arch); console.log('Process PID:', process.pid); console.log('Working directory:', process.cwd());

output:
$ node node-version-check.js Node.js version: v22.20.0 Node.js executable path: /.../.../.nvm/versions/node/v22.20.0/bin/node Platform: linux Architecture: x64 Process PID: 333990 Working directory: /../../...

MCP:
{ "mcpServers": { "chrome-devtools": { "command": "npx", "args": [ "chrome-devtools-mcp@latest", "--headless=true", "--browserUrl=http://127.0.0.1:9222", "--logFile=/tmp/chrome-devtools-mcp-log.txt", "--user-data-dir=~/chrome-remote-debug" ] } } }