@feedmob/github-issues 1.0.0 → 1.0.1

package/README.md

@@ -35,7 +35,7 @@ npm run build
 
 ### Example MCP Client Config (stdio)
 
-**Recommended (avoids completions capability issue):** run from the built artifact when you have the repo. After `npm run build` in `src/github-issues/`:
+**Optional:** run from the built artifact when you have the repo. After `npm run build` in `src/github-issues/`:
 
 ```json
 {
@@ -54,7 +54,7 @@ npm run build
 }
 ```
 
-Alternatively, use `npx` (do **not** use `npm install -g @feedmob/github-issues`; global install ignores the package’s SDK override and can cause the “Server does not support completions” error):
+Alternatively, use `npx` (avoid global install so the correct dependencies are used):
 
 ```json
 {
@@ -152,23 +152,6 @@ npx tsx index.ts
 
 ## Troubleshooting
 
-### `Server does not support completions (required for completion/complete)`
-
-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.
-
-**Fix:**
-
-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:
-   ```json
-   "command": "node",
-   "args": ["/absolute/path/to/fm-mcp-servers/src/github-issues/dist/index.js"]
-   ```
-   Run `npm install` and `npm run build` in `src/github-issues/` first.
-
-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.
-
-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.
-
 ### `SyntaxError: Unexpected token ':'` with JSON on stdin
 
 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

@@ -1,3 +1,3 @@
 // If the format of this file changes, so it doesn't simply export a VERSION constant,
 // this will break .github/workflows/version-check.yml.
-export const VERSION = "0.0.9";
+export const VERSION = "1.0.1";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@feedmob/github-issues",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "MCP server for using the GitHub API",
   "license": "MIT",
   "author": "FeedMob",
@@ -19,11 +19,10 @@
     "watch": "tsc --watch"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "1.21.2",
     "@types/node": "^22",
     "@types/node-fetch": "^2.6.12",
     "date-fns": "^4.1.0",
-    "fastmcp": "2.1.0",
+    "fastmcp": "^3.33.0",
     "node-fetch": "^3.3.2",
     "universal-user-agent": "^7.0.2",
     "zod": "^3.22.4",
@@ -36,8 +35,5 @@
   "repository": {
     "type": "git",
     "url": "https://github.com/feed-mob/fm-mcp-servers"
-  },
-  "overrides": {
-    "@modelcontextprotocol/sdk": "1.21.2"
   }
 }