Chronic MCP Server failure

Describe the Bug

My MCP Server tools are constantly failing and I must restart Cursor to get them back, which only sometimes works. It seems to happen constantly with Desktop Commander, Context7, Puppeter, well actually everything I use. I am looking at my MCP list right now and 3 out of 7 are working with many stuck at “Loading tools” such as Github MCP. I always ensure there are no errors in my syntax for the mcp.json and most of my MCPs are SSE from Smithery, Github, etc. I can guarantee I will have MCPs stopping during any coding session and so when I return from a break the agents are inevitably stuck by 1 of the MCPs so I usually must disable all the MCPs because any one could fail and hang up progress. I would love to know this was my fault so I can correct it. Thank you!

Steps to Reproduce

I can reproduce this bug by attempting to use Desktop Commander 3-4 times before it stops working. There is no graceful shutdown either to let me debug it.

Expected Behavior

The MCP should work and if it does fail, there is a message in the chat window alerting me so I don’t get so frustrated at the randomness and the “Generating…” being stuck mode. While I’m waiting for progress. It makes me mentally link my frustration with Cursor, an IDE I love to use!

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

1.2.4 (wish there were a copy button on this guys!)

Additional Information

Along with the dreaded “Running Terminal Command…” Cursor is in an unusable state for me and so I must jump over to Kilo or Trae.

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. In the future, we might add a server failure warning. However, in your specific case, clearing the cache might help.

Try clearing the package cache:

macOS/Linux: ~/.npm/_npx
Windows: %LocalAppData%/npm-cache/_npx

Then restart Cursor.

Fantastic news that you’re considering a server error message. I’ll give that a shot today.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.