Please increase the MCP tool limit beyond the current cap of 40, as MCP tools are gaining popularity and expanding with additional functionalities. Some MCP servers host more than 10 tools and even some are 20+, making it difficult to accommodate them within the existing limit while integrating with other MCP servers.
3 Likes
The 40 tool limit (Cursor – Model Context Protocol) is actually there for a good reason - if we increased it, the AI would struggle to effectively choose between all the available tools
We’re working on a better system for the AI to intelligently select the right tools. For now, the best approach is to manually disable any tools you don’t need within your MCP server to stay under the 40 tool limit
This way you can ensure the tools you actually need are available and working effectively
I do think a nice middle ground option would be the ability to disable certain tools within an MCP. For example the GitHub MCP has a lot of tools available but I mainly want it for code search, i could disable create repo, create/update files, etc.
I understand the authors desire to include as much functionality as they can in their MCPs and that should be encouraged, we just need a way to limit scope it from the users end.
2 Likes
Ability to disable tools is very much needed!
4 Likes
See Add the possibility to filter MCP tools where I request a filtering feature for MCP tools
