-
Notifications
You must be signed in to change notification settings - Fork 80
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
ConnectionError from generated sample #90
Comments
Possibly a dupe of #83. @skylarbpayne just out of curiosity, if you start the inspector with |
Or alternatively, if you run with |
Running with the version pinned to
|
Having trouble repro-ing even with your steps unfortunately. I'll keep trying some things. In the meantime, can you try running against the latest version (0.2.6)? It has some additional changes around the startup logic. |
Also have it working on 0.2.2 when @latest (0.2.6) wouldn't work for me. logs: 0.2.2
0.2.6:
on 0.2.6, all i get is |
@darinkishore super helpful logs, thanks! One thing to try on 0.2.6: Try running just |
Yes, I got the same thing as Darin when I tried When I try running |
The previous command/args that you used are stored in localStorage and used if you don't provide new ones 😄 @skylarbpayne @darinkishore we just released 0.2.7, which should address the issue. Thanks for the report, and please feel free to reopen this issue if the problem persists! |
Confirming it works! Thanks! |
Describe the bug
I cannot successfully connect with the MCP Inspector. It was working at one point, but suddenly stopped. Even with a fresh example generated via uvx create-mcp-server.
To Reproduce
Caveat: I am not sure what exactly is causing the broken state; so I'm not sure these are all the steps.
Steps to reproduce the behavior:
uvx create-mcp-server --path example_mcp
cd example_mcp && uv sync --dev --all-extras
npx @modelcontextprotocol/inspector uv --directory /Users/skylarbpayne/projects/example_mcp run example-mcp
> Connect
buttonExpected behavior
I expect the connection to occur successfully
Logs
From the console:
Additional context
At some point it was working, and I was iterating on a server. Then I noticed that something (I think a node library?) updated, and since then it has not worked. I tried restarting my computer, uninstalling all global node packages and starting over.
I also remember there being some logs that would occur after the output of the link to the locally running Inspector when it was working (possibly something that was starting the mcp server?). Now I do not see anything (as if it's not actually starting the server?)
The text was updated successfully, but these errors were encountered: