-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Claude App] "Could not attach to MCP server github" #42
Comments
Are you able to get GitHub working with the MCP Inspector? That might help narrow down whether this is an issue in the desktop app or the server configuration. |
Unfortunaly can't get MCP Inspector to work either 😅 🔍 MCP Inspector is up and running at http://localhost:5173 🚀
[server] 'PORT' n'est pas reconnu en tant que commande interne
[server] ou externe, un programme ex�cutable ou un fichier de commandes.
[server] PORT= node C:\Users\Lymdun\AppData\Local\npm-cache\_npx\5a9d879542beca3a\node_modules\@modelcontextprotocol\inspector\server\build\index.js --env npx --args="@modelcontextprotocol/server-github GITHUB_PERSONAL_ACCESS_TOKEN=ghp_rXXXXXX" exited with code 1``` |
Nevermind, been able to launch it - will open an issue later in Inspector repo, could be easier to launch it from Windows (in my case, had to launch both client & server by myself using npm-cache) And the error when trying to connect: Error in /sse route: Error: spawn npx ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn npx',
path: 'npx',
spawnargs: [ '-y', '@modelcontextprotocol/server-github' ]
} |
That looks like one of the issues I was seeing here: #37 Can you try replacing the command |
You're right, got this on my powershell (using "C:\Program Files\nodejs\npx.cmd"):
Error output from MCP Server:
|
Fixed by adding APPDATA varenv in inspector, now I can receive messages & use tools without issue. Note: mcp-server-github.log is empty |
Just seen this log from npm-cache while toying with Claude App, looks like it is the culprit:
|
Did this come after making changes to the server's code, by chance? I'm a bit confused about how the path in this log is being built, or what's logging |
fwiw, it's likely related to how to spawn npx or the environment. "mcp-server-sqlite" which uses There might be some improvement here,
Note: everything works perfect for me on macos |
No, I was using the stock inspector the whole time along with the stock github-server from npm registry |
Getting this error too for filesystem, github and memory servers |
Sorry folks, we believe there's an issue with Claude Desktop launching MCP servers with I think this is the same root cause as #40, so merging with that issue. |
Heya,
Currently trying to set up MCP server github on my Claude app without success - I always get a notification saying "Could not attach to MCP server github". Note that I can see my config on Settings > Developer.
mcp.logs
Latest version of Claude App
OS: Windows 11
The text was updated successfully, but these errors were encountered: