Why is my MCP red?
When the green light was on, it worked fine, but after a while I went into settings and the red light was on.
Does this mean the MCP is idle? Will it turn on normally if I use the MCP again? There are no error messages.
I wonder if it is something to be concerned about or if there is a problem.
Hey, have you tried restarting Cursor? Usually, this should solve the problem.
this keeps happening. i can barely use context7 once before it goes byebye and have to restart again.
cc @msfeldstein
i think there is a bug where it shows red unnecerssarily, but if it actually stops working it sounds like the server is just crashing
1 Like
I have the same issue, the mcp shows red dot with two tools, but the tools work correctly without crashing, could someone from dev team confirm that this is a known issue or if Cursor needs to “see” something specific to make it green?
2 Likes
yup this breaks all the time. restarting allows it to work for a little and then it breaks again
Try clearing the package cache:
macOS/Linux: ~/.npm/_npx
Windows: %LocalAppData%/npm-cache/_npx
Then restart Cursor.
delete that directory? rm -rf ~/.npm/_npx
Yes, exactly.
I think it is related to Cursor caching issue.
When developing MCP servers, if your server shows red status during debugging (due to bugs, missing deps, etc.), Cursor caches that server name as “tainted.” Even after completely fixing your server code, it will stay red forever with that name.
I analysed this problem and found workaround:
Use completely fresh server names. Just rename it.
See details: Cursor IDE's MCP server name caching Issue - always Red status