From 21a2e5a70a8dce7492f197e1ebee0612429a5b9f Mon Sep 17 00:00:00 2001 From: Rovshan Badirkhanov Date: Mon, 23 Feb 2026 13:08:10 +0400 Subject: [PATCH 1/4] Update troubleshooting for MCP server connection errors Added solutions for MCP server connection issues on Windows 10, including using cmd and absolute path for npx. --- docs/troubleshooting.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index e9f51c037..4b2787015 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -98,3 +98,26 @@ Possible workarounds include: `npx chrome-devtools-mcp --browser-url http://127.0.0.1:9222` - **Use Powershell or Git Bash** instead of WSL. + +### Windows 10: Error during discovery for MCP server 'chrome-devtools': MCP error -32000: Connection closed + +- **Solution 1** Call using `cmd` (For more info https://github.com/modelcontextprotocol/servers/issues/1082#issuecomment-2791786310) + ```json + "mcpServers": { + "chrome-devtools": { + "command": "cmd", + "args": ["/c", "npx", "-y", "chrome-devtools-mcp@latest"] + } + } + ``` + > **The Key Change:** On Windows, running a Node.js package via `npx` often requires the `cmd /c` prefix to be executed correctly from within another process like VSCode's extension host. Therefore, `"command": "npx"` was replaced with `"command": "cmd"`, and the actual `npx` command was moved into the `"args"` array, preceded by `"/c"`. This fix allows Windows to interpret the command correctly and launch the server. + +- **Solution 2** Instead of another layer of shell you can write the absolute path to `npx`: + ```json + "mcpServers": { + "chrome-devtools": { + "command": "C:\\nvm4w\\nodejs\\npx.ps1", + "args": ["-y", "chrome-devtools-mcp@latest"] + } + } + ``` From 63330d5f4d1becbc840f5575c1ea367fcc0553aa Mon Sep 17 00:00:00 2001 From: Rovshan Badirkhanov Date: Wed, 25 Feb 2026 02:43:43 +0400 Subject: [PATCH 2/4] Clarify npx path and file extension usage Added notes on adjusting the npx path and file extensions. --- docs/troubleshooting.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 4b2787015..f28dd7a09 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -121,3 +121,4 @@ Possible workarounds include: } } ``` + Note: The path above is an example. You must adjust it to match the actual location of `npx` on your machine. Depending on your setup, the file extension might be `.cmd`, `.bat`, or `.exe` rather than `.ps1`. Also, ensure you use double backslashes (`\\`) as path delimiters, as required by the JSON format. From 84292a2dd13467791a237e8d1818613ba33c9a79 Mon Sep 17 00:00:00 2001 From: Rovshan Badirkhanov Date: Thu, 26 Feb 2026 23:33:22 +0400 Subject: [PATCH 3/4] Move note upper Move note upper --- docs/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index f28dd7a09..0d451d85d 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -113,6 +113,7 @@ Possible workarounds include: > **The Key Change:** On Windows, running a Node.js package via `npx` often requires the `cmd /c` prefix to be executed correctly from within another process like VSCode's extension host. Therefore, `"command": "npx"` was replaced with `"command": "cmd"`, and the actual `npx` command was moved into the `"args"` array, preceded by `"/c"`. This fix allows Windows to interpret the command correctly and launch the server. - **Solution 2** Instead of another layer of shell you can write the absolute path to `npx`: + > Note: The path below is an example. You must adjust it to match the actual location of `npx` on your machine. Depending on your setup, the file extension might be `.cmd`, `.bat`, or `.exe` rather than `.ps1`. Also, ensure you use double backslashes (`\\`) as path delimiters, as required by the JSON format. ```json "mcpServers": { "chrome-devtools": { @@ -121,4 +122,3 @@ Possible workarounds include: } } ``` - Note: The path above is an example. You must adjust it to match the actual location of `npx` on your machine. Depending on your setup, the file extension might be `.cmd`, `.bat`, or `.exe` rather than `.ps1`. Also, ensure you use double backslashes (`\\`) as path delimiters, as required by the JSON format. From 558af2f46188aa974cbeac2e15cb30785f546ae7 Mon Sep 17 00:00:00 2001 From: Alex Rudenko Date: Thu, 5 Mar 2026 22:28:12 +0100 Subject: [PATCH 4/4] chore: format --- docs/troubleshooting.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 3c475185d..ef299edc4 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -103,6 +103,7 @@ Possible workarounds include: ### Windows 10: Error during discovery for MCP server 'chrome-devtools': MCP error -32000: Connection closed - **Solution 1** Call using `cmd` (For more info https://github.com/modelcontextprotocol/servers/issues/1082#issuecomment-2791786310) + ```json "mcpServers": { "chrome-devtools": { @@ -110,7 +111,8 @@ Possible workarounds include: "args": ["/c", "npx", "-y", "chrome-devtools-mcp@latest"] } } - ``` + ``` + > **The Key Change:** On Windows, running a Node.js package via `npx` often requires the `cmd /c` prefix to be executed correctly from within another process like VSCode's extension host. Therefore, `"command": "npx"` was replaced with `"command": "cmd"`, and the actual `npx` command was moved into the `"args"` array, preceded by `"/c"`. This fix allows Windows to interpret the command correctly and launch the server. - **Solution 2** Instead of another layer of shell you can write the absolute path to `npx`: @@ -132,4 +134,3 @@ If you are using the `--autoConnect` flag and tools like `list_pages`, `new_page 2. Remote debugging is enabled in Chrome via `chrome://inspect/#remote-debugging`. 3. You have allowed the remote debugging connection prompt in the browser. 4. There is no other MCP server or tool trying to connect to the same debugging port. -