[BUG] MCP Servers are not started automatically

Whenever I open a new Cursor window or reload an existing one, MCP servers do not start automatically.

In the console, I can see the following error: Timeout waiting for EverythingProvider

However, after I manually restart any of the servers in the MCP Servers section, everything works again

Cursor Info:
Version: 0.45.7
VSCode Version: 1.96.2
Commit: 6ea842450e04c5537da4d83d51823fae13bb30f0
Date: 2025-01-30T18:32:32.733Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.2.0

1 Like

Bro, do you have any step by step how did you make work the mcp server? Because I have tried so many config about that and I don’t even have success even one

1 Like

Even I follow all of the types of documentations it’s not working, I am so frustrated, even the simple tool like brave search which I already fully config but not even one it’s not working help me guys

Well, for example, to use GitHub MCP you just need to add MCP Server with type: “comman” and use the following command:

env GITHUB_PERSONAL_ACCESS_TOKEN=<TOKEN> npx -y @modelcontextprotocol/server-github

could you share some screenshots and code of what is not working? happy to take a look!

When I open a new window, MCP servers stay like this until I hit reload button on one of them

1 Like

In the latest update (0.45.8) I get better error messages :grin: and it looks like now I need to reload each server individually.

fix coming out in next patch, sorry about this @jimmyn!

1 Like

I have tried that, but it’s not working, I tried also brave search and it’s not also working

Failed to locate tools after 0.45.8 upgrade, it works well in 0.45.6 version.
MCP Type is command(stdio) mode.

find one temporary solution for 0.45.8 bug is
start stdio mode mcp with supergateway (GitHub - supercorp-ai/supergateway: Run MCP stdio servers over SSE.)

and then connect to the same in cursor with sse mode

anyway waiting for official solution

@ericzakariasson Confirming that this is still an issue in 0.45.9

what are the changes on that version? like there’s new feature or what?

Same problem with mcp-neo4j-cypher MCP server,
onlyy using supergateway it works…
npx -y supergateway --stdio “uvx mcp-neo4j-cypher --db-url bolt://localhost --username neo4j --password ■■■”

Hm weird, I get Timeout waiting for EverythingProvider error after window reload or in a new window even with supergateway. Does it work for you?

@ericzakariasson could you take a look please?

1 Like

thanks for reporting this! i’m not exactly sure which version this fix will go out in, but the pr has been merged

2 Likes

Is there a reason for non_programatic method for MCP management?

So this was fun to try:

The bot is a HIDEOUS web dev - and cant draw a hexagon yet…


(this is the MCP that I just thought of today to start - where I have a widget dashboard and Ill have commands to thro widgets at the panel>>>

Lets see how this iteration does:

1 Like

Yes, I confirm. And, the form with the MCP server settings in not saveable (e.g. edit server cmdline) after an MCP server entry is first created.

yes,same problem. only local mcp server work