Cursor limits the amount to tools in MCP to 40, which is an understandable design decision.
Nevertheless, I use 2 MCPs right now, mcp-atlassian and gitlab-mcp. Together, they serve 52 tools. Of those, 20 are totally irrelevant for any workflow I can think about for my work, and 10 more are very seldomly relevant.
One example, today I was prompting something like
Look up issue ABC-123
The model started to look for the issue in Gitlab. 
Being able to selectively enable relevant tools (in mcp.json file?) would help me (as i know that all my tools are passed to the model) and the model (as it only sees the relevant tools).
Please consider implementing such a thing!
7 Likes
I’m in the same boat. I just added github and jira and immediately hit 40 tools limit! my Cursor trial lasted for 10 minutes to learn that it’s kind of useless if you’re trying to make use of MCP tools
Hey, I think we’ll implement this soon.
2 Likes
Hi, any update on this? VSCode has it available and on top I found it pretty well resolved through the UI.
2 Likes
This is available in 0.50 now! You simply click the tool names and they enable/disable.
Improvement ideas:
- when disabling a tool, update the “you have too many tools” warning
- surface the possibility to disable specific tools better (it’s hidden in plain sight…)
But: Thanks for implementing this!
1 Like
Hey, thank you for this feature - I haven’t notice that in changelog! Even after I’ve disabled tools by clicking on them, the cursor message on top doesnt update about “enabled tools” which makes red message stays forever. @Dev
1 Like
