zopkit-bug-resolution-mcp 1.2.0 → 1.2.1
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 +13 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -62,6 +62,19 @@ Published to npm as
|
|
|
62
62
|
elsewhere (e.g. a local dev backend) with an extra env var,
|
|
63
63
|
`BUG_REPORT_API_BASE_URL=http://localhost:3000`.
|
|
64
64
|
|
|
65
|
+
**On Windows**, a bare `npx` command as shown above commonly fails or
|
|
66
|
+
hangs (MCP client "connection timed out after 30000ms") — Windows needs
|
|
67
|
+
`npx.cmd` resolved through `cmd.exe`, not the bare `npx` name spawn()
|
|
68
|
+
looks for on macOS/Linux. Route it through `cmd /c` instead:
|
|
69
|
+
|
|
70
|
+
```bash
|
|
71
|
+
claude mcp add bug-resolution \
|
|
72
|
+
--env BUG_REPORT_API_KEY=<the key you copied> \
|
|
73
|
+
-- cmd /c npx -y zopkit-bug-resolution-mcp
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
or in the JSON config, `"command": "cmd", "args": ["/c", "npx", "-y", "zopkit-bug-resolution-mcp"]`.
|
|
77
|
+
|
|
65
78
|
3. Restart Claude Code (or Claude Desktop) and approve `bug-resolution` when
|
|
66
79
|
prompted.
|
|
67
80
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "zopkit-bug-resolution-mcp",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.1",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "MCP server for Zopkit wrapper bug reports: fetch full bug context (with screenshots), submit how a bug was fixed, list bugs assigned to you, and file new bug reports. Requires a BUG_REPORT_API_KEY (generated in the company-admin panel) — see README.md.",
|
|
6
6
|
"license": "UNLICENSED",
|