Context7 MCP server fails to retrieve library documentation in Claude Desktop #71
Comments
|
Could you please check Claude's logs for errors? You can use the following command: Also just for safe measure could you try telling Claude to use |
|
2025-04-23T11:56:05.606Z [Runner] WebSocket error: Unexpected server response: 524 Here is what I"m seeing in claude desktop, I also can't get this working in vscode with cline or roocode. |
Oh yes, the log, sorry. Then I made a request and it resulted in the errors you see from line 127. The double quote request didn’t work either. |
|
I see It means your Node.js version is < 18. Just upgrading Node.js should solve the problem. @egoes Check your version with Also, both Bun and Deno support fetch natively. So if you’re using |
Could you provide your claude desktop logs please. You can use |
After verifying on two machines, I'm equally running on both: Node
As noted in my initial post, bunx and deno (freshly installed) gave me the same errors. |
|
Here's a simplified explanation of the issue and fix I've worked out with Claude 3.7 :-) : Issue FoundWhen trying to use Context7 MCP server with DataTables, the API calls to This prevents the MCP server from retrieving library documentation, even though the documentation exists on the Context7 website. Noteconfiguration: SolutionI implemented a multi-layered approach to fix this: - const response = await fetch(url);
+ // Options to improve connection reliability
+ const fetchOptions = {
+ headers: {
+ "User-Agent": "Context7-MCP/1.0",
+ "Accept": "application/json",
+ "X-Context7-Source": "mcp-server"
+ }
+ };
+
+ // Attempt direct API fetch with timeout
+ async function safeApiFetch(url: URL, options = {}) {
+ try {
+ const controller = new AbortController();
+ const timeout = setTimeout(() => controller.abort(), 5000);
+
+ const response = await fetch(url, {
+ ...fetchOptions,
+ ...options,
+ signal: controller.signal
+ });
+
+ clearTimeout(timeout);
+ return response;
+ } catch (error) {
+ console.error(`Error fetching ${url}: ${error}`);
+ return null;
+ }
+ }
+
+ // Fallback to CORS proxies when direct access fails
+ async function proxyApiFetch(url: URL) {
+ try {
+ const proxyUrls = [
+ `https://api.allorigins.win/raw?url=${encodeURIComponent(url.toString())}`,
+ `https://corsproxy.io/?${encodeURIComponent(url.toString())}`,
+ `https://proxy.cors.sh/${url.toString()}`
+ ];
+
+ for (const proxyUrl of proxyUrls) {
+ try {
+ const response = await fetch(proxyUrl);
+ if (response.ok) return response;
+ } catch (e) {
+ console.error(`Proxy ${proxyUrl} failed: ${e}`);
+ }
+ }
+ return null;
+ } catch (error) {
+ console.error(`All proxies failed: ${error}`);
+ return null;
+ }
+ }
+
+ // Try multiple fetch methods
+ let response = await safeApiFetch(url);
+
+ // If direct fetch fails, try proxy
+ if (!response || !response.ok) {
+ console.error("Direct fetch failed, trying proxy");
+ response = await proxyApiFetch(url);
+ }Additionally, I added a local cache for common libraries to ensure functionality even when all network methods fail: + // Local documentation cache for common libraries
+ const hardcodedDocs: Record<string, string> = {
+ "datatables/datatables": `TITLE: Initializing DataTables with jQuery
+ // Documentation content here
+ `
+ };
+
+ // Check cache first
+ if (hardcodedDocs[libraryId]) {
+ console.error(`Using hardcoded docs for ${libraryId}`);
+ return hardcodedDocs[libraryId];
+ }This solution ensures the Context7 MCP server remains functional even when facing SSL/networking issues, with graceful degradation to cached content when needed. |
|
@egoes – I was running into this same issue in Cursor and wanted to share what finally worked for me, along with some things I tried that didn’t. The problem:I was seeing runtime errors like fetch is not defined, even though I had a recent version of Node installed via Homebrew. To investigate, I added a small shim using NODE_OPTIONS=--require=./debug-fetch.js to log the runtime Node version and check for fetch availability. To my surprise, it was defaulting to an older system-level Node installation (v16.x) from /usr/local/bin/node, which doesn’t include fetch globally. Things I tried (unsuccessfully)
Despite all this, Cursor still seemed to fall back to the outdated system Node version when launching the MCP. Perplexing. What finally workedI downloaded and installed the latest Node version directly from the official installer: https://nodejs.org/en After doing that, Cursor began correctly using the updated runtime and the issue went away. Hope this helps anyone else running into the same thing. Would love to understand why Cursor doesn’t consistently respect the system’s shell environment or nvm setup. |
|
Hey @egoes were you able to solve it with @jacobzweig 's solution? |
|
Hey, I missed it, sorry. Will give that a go! @jacobzweig did you uninstall the homebrew version first? |
|
@enesgules As I prefer sticking with homebrew installs and thanks to @jacobzweig 's hints, I went digging in my Mac for older installed files. I first poked around to search for potential other The other route I was about to try, but didn't have to, was to eventually install the node fetch package globally Thanks all for your kind help. |
|
Great! Let us know if you encounter other errors. |
just wanted to +1 this that fix also worked for me! not sure what exactly what was conflicting, but deleting old, unused versions of node in |
Description
I'm encountering an issue with the Context7 MCP server integration in Claude Desktop. While the server connection appears to be working, it consistently fails to retrieve library documentation, despite successful configuration and operation in Claude Code.
Environment
Steps to Reproduce
What Happened
When attempting to resolve library IDs or retrieve documentation:
Typical error:
Or when trying direct document retrieval:
What Was Expected
Successful resolution of library IDs and retrieval of documentation, as experienced in Claude Code environment.
Additional Context
claude mcp add context7 -- npx -y @upstash/context7-mcp@latestbunxinstead ofnpxdeno@latesttagThank you for your help resolving this issue!
The text was updated successfully, but these errors were encountered: