Cursor seems to always run 3x MCP servers. Yes, even when nothing is really used. It seems to start them up together with Cursor (which can be quite resource intensive when for example docker is used to run them!) and also always runs them 3x for some reason.
Hey, the MCP servers you choose to use are not written or controlled by Cursor, simply executed by it.
If the servers are using high resources on your machine, you’d have to look at the implementation of the specific MCP server!
Thank you for the response @danperks 
Perhaps I miscommunicated this in a way that caused you to think that I am pointing to a MCP CPU usage. The problem I posted about is 101% Cursor related - it is a BUG in Cursor.
Cursor is starting the MCP servers as soon as Cursor starts or a server is added. When a server is added to the MCP list in Cursor, Cursor will start this server and the little light will go green.
The problems:
- It seems that Cursor will sometimes start multiple copies of the same server for no reason.
- Also it seems that Cursor will start the MCP servers, without anyone asking it to - it will always keep em running, even if nobody asked the AI anything.
- If Cursor is quit, the MCP servers keep running. If you start Cursor again, it boots up new MCP servers instead of using the old one.
Instead, what Cursor should do is - NOT start any servers at any point, except when it explicitly wants to offer them to AI.
Hope this clarifies it Here is also a video to illustrate: https://www.dropbox.com/scl/fi/3bnqewu20r803k1oyig24/Screen-Recording-2025-02-20-at-17.09.27.mov?rlkey=hxxemuvzpysl1n51581nrjq2a&st=lv9ujdww&dl=0
- Will raise to the team, thanks
- A server could take a while to setup in some cases, so we keep it running so it’s always available. Putting them to “sleep” may not be a bad idea for the future though
- This shouldn’t happen, will flag to the team!
1 Like