getting error #19
Comments
|
+1 have the same issue |
|
I have the same issue, the mcp server for cursor isn't working. I'm using windows. |
|
+1, I have the same error. |
|
I have the same error. |
|
Running Cursor (Linux) also get "client closed". |
|
Could you please try Also at which point this started to happen? The first install? Or when you tried to reload the server? |
|
For windows could you try this please: |
First install. bunx gives me the same error "client closed". |
|
Same here, using MacOS, Cursor, tried both npx and bunx |
|
The error Run Ensure Node.js is in your PATH. |
This is what I get. $ npx -v $ which nodejs $ nodejs -v My guess that it could be releated that Cursor runs as appimage. I will get back here later when I can google some more. |
|
Hm... this is strange. Last message before I left I had troubleshooted for about 20 minutes. Has it been self-resolved? Does it work for you now? |
no
|
|
For Windows user: Create npm folder in this path:
|
its already there 18-04-2025 21:20 .18-04-2025 21:20 .. 18-04-2025 21:20 439 context7-mcp 18-04-2025 21:20 350 context7-mcp.cmd 18-04-2025 21:20 905 context7-mcp.ps1 23-02-2025 21:42 407 cordova 23-02-2025 21:42 334 cordova.cmd 23-02-2025 21:42 841 cordova.ps1 23-03-2025 16:57 423 http-server 23-03-2025 16:57 342 http-server.cmd 23-03-2025 16:57 873 http-server.ps1 12-02-2025 19:57 411 lt 12-02-2025 19:57 336 lt.cmd 12-02-2025 19:57 849 lt.ps1 23-02-2025 17:50 445 next-on-pages 23-02-2025 17:50 353 next-on-pages.cmd 23-02-2025 17:50 917 next-on-pages.ps1 18-04-2025 21:20 node_modules 14-02-2025 17:15 405 npm 14-02-2025 17:15 333 npm.cmd 14-02-2025 17:15 837 npm.ps1 14-02-2025 17:15 405 npx 14-02-2025 17:15 333 npx.cmd 14-02-2025 17:15 837 npx.ps1 19-01-2025 13:13 403 pnpm 19-01-2025 13:13 332 pnpm.cmd 19-01-2025 13:13 833 pnpm.ps1 19-01-2025 13:13 403 pnpx 19-01-2025 13:13 332 pnpx.cmd 19-01-2025 13:13 833 pnpx.ps1 23-02-2025 14:04 405 tsc 23-02-2025 14:04 333 tsc.cmd 23-02-2025 14:04 837 tsc.ps1 23-02-2025 14:04 415 tsserver 23-02-2025 14:04 338 tsserver.cmd 23-02-2025 14:04 857 tsserver.ps1 23-02-2025 17:48 417 wrangler 23-02-2025 17:48 339 wrangler.cmd 23-02-2025 17:48 861 wrangler.ps1 23-02-2025 17:48 417 wrangler2 23-02-2025 17:48 339 wrangler2.cmd 23-02-2025 17:48 861 wrangler2.ps1 39 File(s) 20,930 bytes 3 Dir(s) 32,650,571,776 bytes free C:\Users\r3versein\AppData\Roaming\npm> |
|
Would anyone be interested to hop on a call and share their screen so that we can try to solve the issue together? I can't reproduce it. |
Doesn't work for me |
|
I got the same issue. using Cursor 0.49.2 and macOS. when I change the mcp configuration to the following it works but I got a different issue then: When the MCP tool "get-library-docs" is used, it fails because the parameter is at 2000 tokens. But it says it has to be at 5000 Parameters: Result:
When I tell the agent to use at least 5000 tokens it works. |
|
So the LLM doesn’t correct its error on its own here? Do you think we should completely remove the minimum limit? In our tests, we saw that without the limit, LLMs tend to use very small context windows and don’t really benefit from using Context7. |
Unfortunately the agent/ LLM doesn't correct the token parameter (tried different models - all the same). I got it working for me with this MCP config with Cursor 0.49.2 and macOS, so the used parameter always 5000 token, which is in my opionion definitely needed because like you already said the LLM doesn't benefit from such small context.
So it uses minimum 5000 tokens and it never gets down the 5000 token |
|
This is a quick note for anyone encountering MCP issues on Windows. This config didn't work for me: {
"mcpServers": {
"context7": {
"command": "npx",
"args": ["-y", "@upstash/context7-mcp@latest"]
}
}
}It kept throwing an error when launching the MCP server. After some digging, I found that Windows doesn’t handle Switching to this fixed the problem: {
"mcpServers": {
"context7": {
"command": "cmd /c npx",
"args": ["-y", "@upstash/context7-mcp@latest"]
}
}
}So if you're on Windows and MCP isn't starting, try using |
not working either , bunx works though |
|
Not working for me as well. Client closed error on mac os with apple silicon |
|
For those encountering a similar installation issue, here's how I resolved it: If you're seeing an error like this: The error In my case, I encountered a slightly different issue where the client repeatedly closed, shown by errors like: I resolved this by modifying the MCP configuration to remove the Here's my updated MCP configuration: I'm unsure why omitting 
|
|
Could you please try this which is not ideal but might fix the issue: #47 (comment) |
|
For Cursor Windows users. Try this: Build it in docker. Then use this in cursor mcp: Good luck.. |
|
Yes with docker works. Here is instruction: Building and Running Context7 MCP Docker Image and ConfigurationThis guide will walk you through the steps to build a Docker image for the Prerequisites:
Steps:
After completing these steps, the |
We have updated this in this PR: #69 Instead of returning an error we transform it to 5000 tokens. |
|
Mcp server seems to work but the request seems to fail. You have a stable internet connection right. Could you try eith other libraries please? Which version of the mcp server are you using? |
|
For me, upgrading my global system level nodejs v18->v20, updating PATH var, AND cleaning npm cache finally helped to launch context7 MCP server (I run Cursor on Mac) Better Cursor MCP logs would definitely help debugging this..... they are seriously lacking info |
|
Out of curiosity, anyone who managed to get this to work uses WSL2? |
|
If you are using Cursor with WSL2, you need the following configuration in your {
"mcpServers": {
"context7": {
"command": "wsl",
"args": [
"bash",
"-c",
"'/home/user/.bun/bin/bunx -y @upstash/context7-mcp@latest'"
],
"enabled": true
}
}
}Replace |
|
why everyone having issues @team
…On Sun, May 4, 2025 at 7:48 PM Gary Sassano ***@***.***> wrote:
*garysassano* left a comment (upstash/context7#19)
<#19 (comment)>
If you are using Cursor with WSL2, you need the following configuration in
your mcp.json:
{
"mcpServers": {
"context7": {
"command": "wsl",
"args": [
"bash",
"-c",
"'/home/user/.bun/bin/bunx -y @***@***.***'"
],
"enabled": true
}
}
}
Replace /home/user/.bun/bin/bunx with the absolute path to your npx or
bunx binary. You can find the absolute path by running which npx or which
bunx.
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRXJSERFOMAUG7BUHF2RMD24YSFBAVCNFSM6AAAAAB3NFBKKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBZGI2TSNRRGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Neither Nor Spinning it in standalone mode works fine Getting regular errors like the others |
{
"mcpServers": {
"github.com/upstash/context7-mcp": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@upstash/context7-mcp@latest"
],
"disabled": false,
"autoApprove": []
}
}
} |
|
Hey @citizenll ff this windows config works fine would you mind creating a PR? |
|
Hey @djedlajn could you try smithery please? |
|
Hey @fisforfaheem have you tried using Smithery? |
|
I ran into the same issue, but I figured it out. Here's my scenario: |
|
I was able to resolve this (in cursor mac) using the version from docs instead of 'latest': |
|
1.0.7 is out @eybarta |
|
I had the same issue with npx — the terminal said zsh: command not found: npx. This is also a common problem. brew install node Or you can download the installer from the official Node.js website: Also you can ask Cursor: It's going to do all the things above by itself. |
@enesgules Here #166 |
|
use My node version is 22 btw |
|
I use both of wsl2 and macos. Meanwhile, I use fnm for managing nodejs version. I met this problem on both systems. And I think I figure out the reason and solution. No matter you use cline or Cursor. in macos using context7 mcp server by Cursor: Hope it can help you. |
|
Had issues with @upstash/context7-mcp@latest using Curson on mac - which grabs the latest version. Having versioning working would be good. What worked for me was the following { |
|
this works in windows
and if you have a key from smithery.ai ( https://smithery.ai/server/@upstash/context7-mcp ) then you can also use this
make sure you installed nodejs ( https://nodejs.org/en/download )
Versions: node --version cursor: 0.49.6 I hope it helps |
|
no
…On Mon, May 12, 2025 at 1:51 PM Ertan Dagistanli ***@***.***> wrote:
*ertan2002* left a comment (upstash/context7#19)
<#19 (comment)>
this works in windows
{ "mcpServers": { "context7": { "command": "npx", "args": ["-y",
***@***.***/context7-mcp"] } } }
and if you have a key from smithery.ai (
***@***.***/context7-mcp ) then you can also use
this
{ "mcpServers": { "context7-mcp": { "command": "npx", "args": [ "-y",
***@***.******@***.***", "run", ***@***.***/context7-mcp", "--key",
"YOUR_KEY" ] } } }
make sure you installed nodejs ( https://nodejs.org/en/download )
and then open command line and type npx to ensure if it works. If yes then
you can us the json that I shared above
Versions:
npx --version
10.9.2
node --version
v22.15.0
cursor: 0.49.6
vs code: 1.96.2
I hope it helps
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRXJSCTNE7ZAYPNIEYXECL26BOJ7AVCNFSM6AAAAAB3NFBKKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZRGU3DKNRXHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@fisforfaheem have you tried without the @latest tag or with smithery? |
This works for me. Windows |
tried every suggestion above... |
|
Hey @Avi-E-Koenig what is your node version? |
23.10 |
|
Could you make sure you are using this node? You could try adding the entire path to your config. |
|
Also please try smithery or bun |
|
ok upon further troubleshoot this was a PATH issue with |
and others
The text was updated successfully, but these errors were encountered: