Hello Cursor Team and Community,
I hope this discussion finds you well! I wanted to bring up an important issue that many of us developers are encountering: the current limitation on MCP (Model Context Protocol) tools that’s affecting our development workflows.
Current Situation
Many users are currently seeing an “Exceeding total tools limit” warning when working with MCP tools in Cursor. This limitation is significantly impacting productivity, especially for developers who rely on multiple MCP tools for comprehensive development workflows.
Why This Matters
MCP tools have revolutionized how we interact with various services and systems directly from our development environment. They enable us to:
- Enhanced Productivity: Access to multiple tools simultaneously allows for seamless workflow integration
-
- Better Context Management: Different tools serve different purposes - file management, API interactions, database queries, etc.
-
- Comprehensive Development: Complex projects often require multiple specialized tools working in harmony
The Problem
The current tool limit prevents developers from:
- Using comprehensive tool suites that require 10+ tools
-
- Leveraging the full potential of MCP ecosystem
-
- Building complex, multi-service applications efficiently
-
- Maintaining productive development workflows
Proposed Solutions
- Increase the Default Limit: Raise the current limit to accommodate modern development needs (perhaps 25-50 tools)
- Tiered Limits: Implement different limits based on subscription tiers:
-
- Free users: Current limit
-
- Pro users: Higher limit (25-30 tools)
-
- Enterprise users: Even higher or unlimited
- Dynamic Loading: Allow selective tool loading/unloading during development sessions
- Configuration Options: Let users configure which tools are most critical for their workflow
Impact on Community
This enhancement would:
Improve developer satisfaction and productivity
-
Better leverage the growing MCP ecosystem
-
Support more complex development workflows
-
Attract more developers to the Cursor platform
Community Input Needed
I’d love to hear from other developers:
- How is the current limit affecting your workflow?
-
- What would be an ideal number of MCP tools for your use case?
-
- Are there specific tool combinations that are essential for your work?
Conclusion
Increasing the MCP tools limit would be a significant quality-of-life improvement for the developer community. It would enable us to fully utilize the powerful MCP ecosystem that Cursor has helped create.
Thank you for considering this request, and I look forward to hearing thoughts from both the team and community!
Best regards,
The Community