@upstash/context7-mcp 2.2.2 → 2.2.3

package/dist/index.js

@@ -197,7 +197,7 @@ server.registerTool("query-docs", {
 
 You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.
 
-Do not call this tool more than 3 times per question.`,
+Workflow: call first without researchMode. If that doesn't answer the question, retry with researchMode: true. Do not call each tool more than 3 times per question.`,
     inputSchema: {
         libraryId: z
             .string()
@@ -205,6 +205,10 @@ Do not call this tool more than 3 times per question.`,
         query: z
             .string()
             .describe("The question or task you need help with. Be specific and include relevant details. Good: 'How to set up authentication with JWT in Express.js' or 'React useEffect cleanup function examples'. Bad: 'auth' or 'hooks'. 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."),
+        researchMode: z
+            .boolean()
+            .optional()
+            .describe(`Retry the query with deep research: spins up sandboxed agents that read the actual source repos and runs a live web search, then synthesizes a fresh answer. Set true on retry if you weren't satisfied with the first answer and want a more thorough one. Requires an API key. You can get one free at https://context7.com.`),
     },
     annotations: {
         readOnlyHint: true,
@@ -212,16 +216,46 @@ Do not call this tool more than 3 times per question.`,
         openWorldHint: true,
         idempotentHint: true,
     },
-}, async ({ query, libraryId }) => {
-    const response = await fetchLibraryContext({ query, libraryId }, getClientContext());
-    return {
-        content: [
-            {
-                type: "text",
-                text: response.data,
-            },
-        ],
-    };
+}, async ({ query, libraryId, researchMode }, { sendNotification, _meta }) => {
+    // Emit periodic progress notifications while the upstream call is in flight.
+    // MCP clients that opt into resetTimeoutOnProgress (e.g. opencode) reset their
+    // request timer on each notification, which keeps long-running tools (notably
+    // researchMode) alive past the SDK's default 60s wall-clock timeout. Clients
+    // that don't pass a progressToken simply never see these, so behavior is unchanged.
+    const progressToken = _meta?.progressToken;
+    let progressInterval;
+    if (researchMode && progressToken !== undefined) {
+        let progress = 0;
+        progressInterval = setInterval(() => {
+            progress += 1;
+            sendNotification({
+                method: "notifications/progress",
+                params: {
+                    progressToken,
+                    progress,
+                    message: "Researching documentation...",
+                },
+            }).catch(() => {
+                // Notifications are best-effort; swallow transport errors so the tool
+                // call itself isn't aborted by a notification write failure.
+            });
+        }, 20_000);
+    }
+    try {
+        const response = await fetchLibraryContext({ query, libraryId, researchMode }, getClientContext());
+        return {
+            content: [
+                {
+                    type: "text",
+                    text: response.data,
+                },
+            ],
+        };
+    }
+    finally {
+        if (progressInterval)
+            clearInterval(progressInterval);
+    }
 });
 async function main() {
     const transportType = TRANSPORT_TYPE;
@@ -309,9 +343,14 @@ async function main() {
                     clientInfo: extractClientInfoFromUserAgent(req.headers["user-agent"]),
                     transport: "http",
                 };
+                // Use SSE responses for tool calls (enableJsonResponse: false). The SDK then
+                // flushes response headers immediately after parsing the request rather than
+                // buffering until the tool returns. This is required for long-running tools
+                // (e.g. researchMode) because some MCP HTTP clients cap the underlying fetch
+                // at 60s waiting for headers, even though the per-tool timeout is much higher.
                 const transport = new StreamableHTTPServerTransport({
                     sessionIdGenerator: undefined,
-                    enableJsonResponse: true,
+                    enableJsonResponse: false,
                 });
                 res.on("close", () => {
                     transport.close();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@upstash/context7-mcp",
-  "version": "2.2.2",
+  "version": "2.2.3",
   "mcpName": "io.github.upstash/context7",
   "description": "MCP server for Context7",
   "repository": {