-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MCP servers fail to connect with npx
on Windows
#40
Comments
Can you share your |
You should use the You can try:
|
Are you able to get the GitHub server working with the MCP Inspector? That will help narrow down whether this is a desktop app issue, or a problem with the server setup. |
Update: just tried on my windows machine, and got the exact same result. Is it possible this is geoblocked in Australia? |
Update on my end, I switched over to a MacBook as there seemed to be some issues with running this on Windows see: modelcontextprotocol/inspector#76 For the filesystem server it is now working as well as the Github server. The region locked theory is wrong, it's just device configuration/OS support. For the SQLite and Brave Search the issues #37 #42 may be helpful for the others in this thread as there seems to be some issues with pathing sometimes - though I am still facing issues on Windows. |
You're quite right. I had a typo in the path to my DB! That was crashing things, even stopping me from adding other tools. |
I'm also experiencing issues with the filesystem server on Windows. Here's my configuration: {
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"C:\\Users\\Username\\Desktop"
]
}
}
} |
Same behavior on Windows 11 and Mac OS. Claude desktop 0.71.1 version on both devices. |
The same problem with me. My configuration : {
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"A:\\Desktop\\"
]
}
}
} |
Experiencing similar issues on Mac OS using Claude Desktop 0.71.1. |
I am having the same issue on Windows 10 with latest Claude Desktop |
@mckaywrigley what does your config file look like?
|
Here's what works for me (mac): TL;DR Try using an absolute path and specify the latest Python version in claude_desktop_config.json when configuring Detailed version: I followed the sqlite instructions but ran into a "Could not connect to MCP server sqlite" error. The fix was to use an absolute path in claude_desktop_config.json, e.g. > which uvx
/usr/local/Homebrew/bin/uvx After restarting Claude, the "Attach from MCP" button still wasn't appearing next to "Upload files" button.
Since i have a newer Python installed (via miniconda), I resolved this by passing an extra My full JSON config file: {
"mcpServers": {
"sqlite": {
"command": "/usr/local/Homebrew/bin/uvx",
"args": [
"--python",
"/usr/local/Homebrew/Caskroom/miniconda/base/bin/python3",
"mcp-server-sqlite",
"--db-path",
"/Users/<user>/test.db"
]
}
}
} |
@thenameless7741 Just to check, are you on an Intel Mac? |
Sorry folks, and thanks for your patience! For As a workaround, you should be able to |
@jspahrsummers I'm still using the old Homebrew setup on my M1 and haven't migrated over to the /opt directory yet. I suspect there are a few others out there in the same boat as me. |
@jspahrsummers FYI, I'm using Windows. The memory server is installed globally, but it’s still not working. The closest I’ve gotten is with this config, which starts the server, but after 1 minute, Claude shows the same error: 'Couldn't attach...' "mcpServers": { |
@oscarcalvo As @jspahrsummers mentioned, you have to use node directly, like this
|
@rkaradas You are right, thanks |
Any ways to access mcp-server inside WSL? I've tried this but no luck:
|
THANKS YOU !!!!!!! |
Since this is an issue with the system not knowing what version of node to use, (whether it is because of nvm or different versions on the system) it seems like the for sure way to solve this is to explicitly state the version of node if you can. This issue is also stated in this thread regarding nvm: #64 Once you point to the correct node version, use the corresponding index.js file in the argument for the server you want to connect to. This is what i did on MacOS:
|
@natefikru just tried this method on Windows 10 unfortunately it didn't work (for the "xxx" I used my real keys just changed it for this btw) |
Fixing MCP Server Connection Issues in Claude DesktopInstallation Steps1. Install Required Packagesnpm install -g @modelcontextprotocol/server-filesystem
npm install -g @modelcontextprotocol/server-memory
npm install -g @modelcontextprotocol/server-brave-search
npm install -g @modelcontextprotocol/server-github 2. Update ConfigurationReplace content in {
"mcpServers": {
"filesystem": {
"command": "node",
"args": [
"C:/Users/YOUR_USERNAME/AppData/Roaming/npm/node_modules/@modelcontextprotocol/server-filesystem/dist/index.js",
"c:/"
]
},
"memory": {
"command": "node",
"args": [
"C:/Users/YOUR_USERNAME/AppData/Roaming/npm/node_modules/@modelcontextprotocol/server-memory/dist/index.js"
]
},
"git": {
"command": "uvx",
"args": [
"mcp-server-git",
"--repository",
"C:/Users/YOUR_USERNAME/Projects/NodeJs/super_ai_agents"
]
},
"brave-search": {
"command": "node",
"args": [
"C:/Users/YOUR_USERNAME/AppData/Roaming/npm/node_modules/@modelcontextprotocol/server-brave-search/dist/index.js"
],
"env": {
"BRAVE_API_KEY": "YOUR_BRAVE_API_KEY"
}
},
"github": {
"command": "node",
"args": [
"C:/Users/YOUR_USERNAME/AppData/Roaming/npm/node_modules/@modelcontextprotocol/server-github/dist/index.js"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_GITHUB_TOKEN"
}
}
}
} Note: Replace 3. Test Server ConnectionsRun these commands individually to verify each server: node C:/Users/YOUR_USERNAME/AppData/Roaming/npm/node_modules/@modelcontextprotocol/server-filesystem/dist/index.js c:/
node C:/Users/YOUR_USERNAME/AppData/Roaming/npm/node_modules/@modelcontextprotocol/server-memory/dist/index.js
node C:/Users/YOUR_USERNAME/AppData/Roaming/npm/node_modules/@modelcontextprotocol/server-brave-search/dist/index.js
node C:/Users/YOUR_USERNAME/AppData/Roaming/npm/node_modules/@modelcontextprotocol/server-github/dist/index.js 4. Final Steps
Success IndicatorsLook for these messages in the logs:
Important Notes
|
How I enabled the MCP Brave Search. In Windows, really pay attention to the absolute pathFollowing steps by @Chatmala , i make a few adjustment below:
Steps:
|
@ymdarum Your solution works as well when using nvm for windows. Good Catch Man! You nailed it! |
@ymdarum it worked! |
@ymdarum thanks man, this worked for me as well |
thank you soooooooomuch for this! it worked for me too
…On Sun, Dec 1, 2024 at 3:38 PM Angelo Alexander ***@***.***> wrote:
@ymdarum <https://github.com/ymdarum> thanks man, this worked for me as
well
—
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM22A2N3JGAILBLC27PQL7T2DNXUVAVCNFSM6AAAAABSO4TCKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGI2DCOJUGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
*. | Fabien Dostie*
.///Direction Technique / Network Admin / Post-Production Specialist
.//Coloriste Resolve / Compositing / Online Editing / AR - VR
./DIT / DMT / Technicien Scene Video (AQTIS 514 - IATSE 56)
C: 438.357.3462 W: fabiendostie.com lefab.biz
|
Actually there is similar problem with python based MCP servers . When I try to run it with uvx it fails but when I run it with python command it works fine. I think the MCP servers should be ran in more ancient way using python or npm rather than uvx or npx. |
Also why in the world is there no linux app of Claude . While more than 90% of development is done on Linux . This is really sad and mine boggling. |
🎉this works for me : {
"mcpServers": {
"git": {
"command": "python3.11",
"args": [
"-m",
"mcp_server_git",
"--repository",
"C:\\Users\\heman\\Desktop\\test_mcp_git"
]
},
"memory": {
"command": "node",
"args": [
"C:\\Users\\heman\\AppData\\Roaming\\npm\\node_modules\\@modelcontextprotocol\\server-memory\\dist\\index.js"
]
},
"filesystem": {
"command": "node",
"args": [
"C:\\Users\\heman\\AppData\\Roaming\\npm\\node_modules\\@modelcontextprotocol\\server-filesystem\\dist\\index.js",
"C:\\Users\\heman\\Desktop",
"C:\\Users\\heman\\Desktop\\test_mcp_git"
]
},
"github": {
"command": "node",
"args": [
"C:\\Users\\heman\\AppData\\Roaming\\npm\\node_modules\\@modelcontextprotocol\\server-github\\dist\\index.js"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "my-token"
}
}
}
} |
Faced the same issue in Mac because my node is setup using node version manager {
"mcpServers": {
"github": {
"command": "/Users/<me>/.asdf/shims/npx",
"args": [
"-y",
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": ""
}
}
}
} |
i am on a windows pc and my servers for filesystem, brave, etc work fine
} would appreciate any guidance on how to get the gdrive mcp to work, please. thx! |
my OS is windwos 11 23h2. I found that even killed all claude tasks, you also need to kill the node.exe process(es, sometime, here were 2 node.exe tasks. ) the guide file "https://modelcontextprotocol.io/quickstart#file-system-access" or sample file "https://github.com/dave2nian/servers/tree/main/src/filesystem" in args part "-y" that mean is auto answer to keep communication with MCP filesystem server. but node.js is a event driven service, it don't need to keep the link. so I tried to change args from -y to /c. know it is working. |
Hey folks, there's a new version of Claude Desktop that should resolve issues launching Thanks for your patience! |
Our updater is a bit quieter than we'd like, the short version to force the update is, "Help => Check for updates", wait some time, then "File => Exit" and restart the app |
This worked for me almost. I just had to replace my local /node_modules/@modelcontextprotocol location. It wasn't the same place as this because I have NVM installed and it was off the NVM directory. BUT NOW IT WORKS!!!!!!!~ THANK YOU EVERYONE |
OMG, just as I got it fixed and now there is a new version of Claude desktop. Lets go back to the original *config.json and see if it works without the explicit location notation. |
yeah, at least for me, the new update has fixed my connection issue |
I am on Windows with the latest desktop version, I have enabled developer mode and I am in Europe
The text was updated successfully, but these errors were encountered: