upstash · KKonstantinov · Jun 30, 2026 · Jul 17, 2026 · Jul 17, 2026 · Jul 17, 2026
diff --git a/.changeset/modern-mcp-stateless.md b/.changeset/modern-mcp-stateless.md
@@ -0,0 +1,5 @@
+---
+"@upstash/context7-mcp": major
+---
+
+Migrate the MCP server to the v2 SDK and the 2026-07-28 protocol revision. HTTP serving is now stateless for both modern and legacy clients, Redis-backed sessions are removed, and the minimum supported Node.js version is 20.
diff --git a/.env.example b/.env.example
@@ -3,8 +3,6 @@ CONTEXT7_API_KEY=
 CONTEXT7_API_URL=https://context7.com/api
 
 # MCP HTTP server
-UPSTASH_REDIS_REST_URL=
-UPSTASH_REDIS_REST_TOKEN=
 RESOURCE_URL=
 AUTH_SERVER_URL=
 OPENAI_APPS_CHALLENGE_TOKEN=

diff --git a/docs/resources/troubleshooting.mdx b/docs/resources/troubleshooting.mdx
@@ -7,7 +7,7 @@ This guide helps you resolve common issues when setting up or using Context7 MCP
 
 ## Quick Checklist
 
-- Confirm Node.js v18+ is installed (`node --version`)
+- Confirm Node.js v20+ is installed (`node --version`)
 - Update to the latest Context7 MCP package (`@upstash/context7-mcp@latest`)
 - Verify connectivity with `curl https://mcp.context7.com/ping`
 - Add your API key to the configuration if you hit rate limits
@@ -92,7 +92,7 @@ Use the `--experimental-fetch` flag:
 
 ### Node.js Version
 
-Ensure you're using Node.js v18 or higher (`node --version`).
+Ensure you're using Node.js v20 or higher (`node --version`).
 
 ## Platform-Specific Issues
 

diff --git a/packages/mcp/README.md b/packages/mcp/README.md
@@ -51,7 +51,7 @@ Check out our [project addition guide](https://context7.com/docs/adding-librarie
 
 ### Requirements
 
-- Node.js >= v18.0.0
+- Node.js >= v20.0.0
 - Cursor, Claude Code, VSCode, Devin Desktop or another MCP Client
 - Context7 API Key (Optional) for higher rate limits and private repositories (Get yours by creating an account at [context7.com/dashboard](https://context7.com/dashboard))
 
@@ -852,7 +852,7 @@ If you prefer to run the MCP server in a Docker container:
    <summary>Click to see Dockerfile content</summary>
 
    ```Dockerfile
-   FROM node:18-alpine
+   FROM node:20-alpine
 
    WORKDIR /app
 
@@ -1592,7 +1592,7 @@ Use the `--experimental-fetch` flag to bypass TLS-related problems:
 1. Try adding `@latest` to the package name
 2. Use `bunx` as an alternative to `npx`
 3. Consider using `deno` as another alternative
-4. Ensure you're using Node.js v18 or higher for native fetch support
+4. Ensure you're using Node.js v20 or higher for native fetch support
 
 </details>
 

diff --git a/packages/mcp/mcpb/manifest.json b/packages/mcp/mcpb/manifest.json
@@ -37,7 +37,7 @@
   "compatibility": {
     "platforms": ["darwin", "win32", "linux"],
     "runtimes": {
-      "node": ">=v18.0.0"
+      "node": ">=v20.0.0"
     }
   },
   "keywords": ["vibe-coding", "developer tools", "documentation", "context"],

diff --git a/packages/mcp/package.json b/packages/mcp/package.json
@@ -32,6 +32,9 @@
   "author": "abdush",
   "license": "MIT",
   "type": "module",
+  "engines": {
+    "node": ">=20"
+  },
   "bin": {
     "context7-mcp": "dist/index.js"
   },
@@ -45,16 +48,17 @@
   },
   "homepage": "https://github.com/upstash/context7#readme",
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.29.0",
+    "@modelcontextprotocol/node": "2.0.0",
+    "@modelcontextprotocol/server": "2.0.0",
     "@types/express": "^5.0.4",
-    "@upstash/redis": "^1.38.0",
     "commander": "^13.1.0",
     "express": "^5.1.0",
     "jose": "^6.2.3",
     "undici": "^6.26.0",
     "zod": "^4.4.3"
   },
   "devDependencies": {
+    "@modelcontextprotocol/client": "2.0.0",
     "@types/node": "^25.0.3",
     "typescript": "^5.8.2",
     "vitest": "^4.1.9"