I don’t know how this is thought thru.. but just by adding github I fill already around 20 Tools…
thats a pointless limit. I have very few MCP-Servers but have already 59 Tools…
i think it needs around 100 as limit or the option to disable some tools you don’t need from a MCP-Server
The actual limit right now is 80, and the next build makes it clearer that 40 is just a limit to warn you that you might be degrading performance, but most models will accept up to 80.
what happens if th limit is reached? since I had the feeling if it goes over the limit of 40 tools, it disables randomly MCP Servers.. could it be?
it woudl very good if you can disable tools fine granularily
it woudl very good if you can disable tools fine granularily
Working on this right now actually
I think one possibility for alleviating this might have to do with custom modes. You can create a custom mode and tell it which MPC servers it has access to. The problem with it is that if the server is disabled, the mode can’t use it.
If cursor made it so that you could turn on tools just for a mode, it could make things smoother. For example, switch to Project Manager role, and I get access to task managment MCP. Web developer role and I get puppeteer. Then the 40/80 tool limit becomes a limit per mode.
Between that and being able to disable individual tools, I think would go a long way toward making MCP much more usable.
Is there a way to restrict the tools an MCP has access to or do you have to accept all of them. For example, I wanted to limit cloudflare-bindings to account, workers, R2, and D1 (no KV Namespaces or Hyperdrive) but 2.5-pro, sonnet-4, etc. couldn’t limit the tools. Would appreciate any solutions.
The new MCP user interface allows you to toggle on/off each MCP tool separately, that helps both for security by not allowing access to features that are not needed and to not pollute context with tools not used.
Each MCP or each MCP tool? cloudflare-bindings comes packaged with 23 tools enabled. I only want about 14 of them. If tools, then how to correctly format in mcp.json?
After you setup the MCP server in the json file, the MCP server will show in the UI and needs to be reloaded/turned on. There you can then enable and disable each tool of each MCP server separately (click on tool name).
Yes that would give you 14 
Actually, i think have more custom mode is the better solution. Becuase, for the fullstack developer, we need to register many mcp server, but some of them just useful for frontend, other just for backend or research. Currently i use the custom mode separate the mcp server into sub set, but only 5 modes is too less.
Thank you!
Agree. I will look into this solution as well. Thanks!
