firefox-devtools-mcp 0.7.1 → 0.7.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +22 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -132,6 +132,28 @@ npm run inspector:dev
|
|
|
132
132
|
- Firefox not found: pass `--firefox-path "/Applications/Firefox.app/Contents/MacOS/firefox"` (macOS) or the correct path on your OS.
|
|
133
133
|
- First run is slow: Selenium sets up the BiDi session; subsequent runs are faster.
|
|
134
134
|
- Stale UIDs after navigation: take a fresh snapshot (`take_snapshot`) before using UID tools.
|
|
135
|
+
- Windows 10: Error during discovery for MCP server 'firefox-devtools': MCP error -32000: Connection closed
|
|
136
|
+
- **Solution 1** Call using `cmd` (For more info https://github.com/modelcontextprotocol/servers/issues/1082#issuecomment-2791786310)
|
|
137
|
+
```json
|
|
138
|
+
"mcpServers": {
|
|
139
|
+
"firefox-devtools": {
|
|
140
|
+
"command": "cmd",
|
|
141
|
+
"args": ["/c", "npx", "-y", "firefox-devtools-mcp@latest"]
|
|
142
|
+
}
|
|
143
|
+
}
|
|
144
|
+
```
|
|
145
|
+
> **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.
|
|
146
|
+
|
|
147
|
+
- **Solution 2** Instead of another layer of shell you can write the absolute path to `npx`:
|
|
148
|
+
```json
|
|
149
|
+
"mcpServers": {
|
|
150
|
+
"firefox-devtools": {
|
|
151
|
+
"command": "C:\\nvm4w\\nodejs\\npx.ps1",
|
|
152
|
+
"args": ["-y", "firefox-devtools-mcp@latest"]
|
|
153
|
+
}
|
|
154
|
+
}
|
|
155
|
+
```
|
|
156
|
+
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.
|
|
135
157
|
|
|
136
158
|
## Versioning
|
|
137
159
|
|