@feedmob/github-issues 1.0.0 → 1.0.2
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 +2 -19
- package/dist/common/version.js +1 -1
- package/package.json +2 -3
package/README.md
CHANGED
|
@@ -35,7 +35,7 @@ npm run build
|
|
|
35
35
|
|
|
36
36
|
### Example MCP Client Config (stdio)
|
|
37
37
|
|
|
38
|
-
**
|
|
38
|
+
**Optional:** run from the built artifact when you have the repo. After `npm run build` in `src/github-issues/`:
|
|
39
39
|
|
|
40
40
|
```json
|
|
41
41
|
{
|
|
@@ -54,7 +54,7 @@ npm run build
|
|
|
54
54
|
}
|
|
55
55
|
```
|
|
56
56
|
|
|
57
|
-
Alternatively, use `npx` (
|
|
57
|
+
Alternatively, use `npx` (avoid global install so the correct dependencies are used):
|
|
58
58
|
|
|
59
59
|
```json
|
|
60
60
|
{
|
|
@@ -152,23 +152,6 @@ npx tsx index.ts
|
|
|
152
152
|
|
|
153
153
|
## Troubleshooting
|
|
154
154
|
|
|
155
|
-
### `Server does not support completions (required for completion/complete)`
|
|
156
|
-
|
|
157
|
-
Cursor (and other MCP clients using protocol 2025-11-25) may request the `completion/complete` capability. FastMCP 2.1 uses `@modelcontextprotocol/sdk`; SDK **1.22.0+** requires the server to advertise the completions capability when registering a completion handler, but FastMCP does not set it, so the server crashes on start.
|
|
158
|
-
|
|
159
|
-
**Fix:**
|
|
160
|
-
|
|
161
|
-
1. **Preferred:** Run from the repo so the package’s SDK pin is used. In Cursor MCP config, use the built server instead of `npx` or a global install:
|
|
162
|
-
```json
|
|
163
|
-
"command": "node",
|
|
164
|
-
"args": ["/absolute/path/to/fm-mcp-servers/src/github-issues/dist/index.js"]
|
|
165
|
-
```
|
|
166
|
-
Run `npm install` and `npm run build` in `src/github-issues/` first.
|
|
167
|
-
|
|
168
|
-
2. **If you use npx:** Avoid `npm install -g @feedmob/github-issues`. npm applies `overrides` only from the root project; a global install has no root `package.json`, so the pin is ignored and the crash can occur. Use `npx -y @feedmob/github-issues` (npx uses the package as root so the override applies), or switch to the local path above.
|
|
169
|
-
|
|
170
|
-
3. **Local dev:** This package pins the SDK to **1.21.2** via `overrides` and a direct dependency. After pulling, run `npm install` in `src/github-issues/` so the pin is applied.
|
|
171
|
-
|
|
172
155
|
### `SyntaxError: Unexpected token ':'` with JSON on stdin
|
|
173
156
|
|
|
174
157
|
If you see Node parsing the MCP `initialize` JSON as JavaScript (e.g. `Expected ';', '}' or <eof>`), the process is likely being run with **stdin as script** (e.g. `node -`). The server must be started with **stdio** so that stdin is the MCP channel, not script input. In Cursor MCP config, use a plain command such as `node /absolute/path/to/dist/index.js` or `npx -y @feedmob/github-issues` with no `-` or stdin-eval.
|
package/dist/common/version.js
CHANGED
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@feedmob/github-issues",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.2",
|
|
4
4
|
"description": "MCP server for using the GitHub API",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "FeedMob",
|
|
@@ -19,11 +19,10 @@
|
|
|
19
19
|
"watch": "tsc --watch"
|
|
20
20
|
},
|
|
21
21
|
"dependencies": {
|
|
22
|
-
"@modelcontextprotocol/sdk": "1.21.2",
|
|
23
22
|
"@types/node": "^22",
|
|
24
23
|
"@types/node-fetch": "^2.6.12",
|
|
25
24
|
"date-fns": "^4.1.0",
|
|
26
|
-
"fastmcp": "
|
|
25
|
+
"fastmcp": "^3.33.0",
|
|
27
26
|
"node-fetch": "^3.3.2",
|
|
28
27
|
"universal-user-agent": "^7.0.2",
|
|
29
28
|
"zod": "^3.22.4",
|