@upstash/context7-mcp 3.2.3 → 3.2.5

package/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.18.1
 - 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
 
@@ -1366,6 +1366,25 @@ See the [Emdash repository](https://github.com/generalaction/emdash) for more in
 
 </details>
 
+<details>
+<summary><b>Install in Autohand Code</b></summary>
+
+Use the [Autohand Code CLI](https://github.com/autohandai/code-cli/) to add the local Context7 server:
+
+```sh
+autohand mcp add context7 npx -y @upstash/context7-mcp --api-key YOUR_API_KEY
+```
+
+Add `--scope project` before `context7` to save the server in the current project's `.autohand` configuration instead of your user configuration.
+
+For basic usage without an API key, you can connect to the remote server instead:
+
+```sh
+autohand mcp add --transport http context7 https://mcp.context7.com/mcp
+```
+
+</details>
+
 ## 🔨 Available Tools
 
 Context7 MCP provides the following tools that LLMs can use:
@@ -1573,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>
 

package/dist/index.js

@@ -129,7 +129,7 @@ IMPORTANT: Do not call this tool more than 3 times per question. If you cannot f
         inputSchema: {
             query: z
                 .string()
-                .describe("The question or task you need help with. This is used to rank library results by relevance to what the user is trying to accomplish. The query is sent to the Context7 API for processing. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query."),
+                .describe("What to look up in the library's documentation. This is used to rank library results by relevance to what the user is trying to accomplish. The query is sent to the Context7 API for processing. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query."),
             libraryName: z
                 .string()
                 .describe("Library name to search for and retrieve a Context7-compatible library ID. Use the official library name with proper punctuation — e.g., 'Next.js' instead of 'nextjs', 'Customer.io' instead of 'customerio', 'Three.js' instead of 'threejs'."),
@@ -180,7 +180,7 @@ Do not call this tool more than 3 times per question.`,
                 .describe("Exact Context7-compatible library ID (e.g., '/mongodb/docs', '/vercel/next.js', '/supabase/supabase', '/vercel/next.js/v14.3.0-canary.87') retrieved from 'resolve-library-id' or directly from user query in the format '/org/project' or '/org/project/version'."),
             query: z
                 .string()
-                .describe("The question or task you need help with, scoped to a single concept. Be specific and include relevant details, but keep each query to one topic — if the user's question spans multiple distinct concepts, make a separate call per concept instead of combining them, unless the question is about how the concepts interact. Good: 'How to set up authentication with JWT in Express.js' or 'React useEffect cleanup function examples'. Bad (too vague): 'auth' or 'hooks'. Bad (too broad): 'routing and auth and caching in Next.js'. The query is sent to the Context7 API for processing. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query."),
+                .describe("What to look up in the library's documentation, scoped to a single concept. Be specific and include relevant details, but keep each query to one topic — if the user's question spans multiple distinct concepts, make a separate call per concept instead of combining them, unless the question is about how the concepts interact. Good: 'How to set up authentication with JWT in Express.js' or 'React useEffect cleanup function examples'. Bad (too vague): 'auth' or 'hooks'. Bad (too broad): 'routing and auth and caching in Next.js'. The query is sent to the Context7 API for processing. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query."),
         },
         annotations: {
             readOnlyHint: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@upstash/context7-mcp",
-  "version": "3.2.3",
+  "version": "3.2.5",
   "mcpName": "io.github.upstash/context7",
   "description": "MCP server for Context7",
   "repository": {
@@ -38,14 +38,17 @@
     "@upstash/redis": "^1.38.0",
     "commander": "^13.1.0",
     "express": "^5.1.0",
-    "jose": "^6.1.3",
-    "undici": "^6.26.0",
+    "jose": "^6.2.3",
+    "undici": "^7.0.0",
     "zod": "^4.4.3"
   },
   "devDependencies": {
     "@types/node": "^25.0.3",
     "typescript": "^5.8.2",
-    "vitest": "^4.0.13"
+    "vitest": "^4.1.9"
+  },
+  "engines": {
+    "node": ">=20.18.1"
   },
   "scripts": {
     "build": "tsc && chmod 755 dist/index.js",