modelcontextprotocol / modelcontextprotocol/servers
"Not connected" error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
On Windows 11:
I was unable to successfully set up the Sequential Thinking MCP server. I encountered a "Not connected" error despite trying various configuration changes and troubleshooting steps. I suspect there might be a deeper issue with the MCP server setup or the extension's handling of MCP servers that I'm unable to resolve with the available tools and information.
When I run:
npx -y @modelcontextprotocol/server-sequential-thinking
I get : Sequential Thinking MCP Server running on stdio
if cline runs it:
Error Error executing MCP tool: Not connected
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue on Windows 11 by running npx -y @modelcontextprotocol/server-sequential-thinking directly, then compare that result with the same server launched by Cline. Trace where the connection changes from the running stdio server to Not connected; done means identifying whether the failure is in the MCP server setup or the extension's handling of MCP servers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100