Cursor Pro Limits MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_usage_statsB | Get current Cursor Pro usage statistics and limits |
| get_service_usageC | Get usage statistics for a specific service |
| check_alertsB | Check for services approaching or exceeding limits |
| update_usageB | Update usage statistics (for testing or manual updates) |
| set_subscription_tierC | Set the subscription tier (pro, pro-plus, ultra) |
| get_subscription_infoB | Get current subscription tier and limits |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have distinct purposes, but 'get_usage_stats' and 'get_service_usage' could be confused as both retrieve usage data. The descriptions clarify that one is for overall Cursor Pro usage and the other for specific services, but the naming overlap might cause misselection. Other tools like 'check_alerts' and 'set_subscription_tier' are clearly unique.
All tools follow a consistent verb_noun pattern using snake_case, such as 'check_alerts', 'get_service_usage', and 'set_subscription_tier'. There are no deviations in naming conventions, making the set predictable and easy to parse for an agent.
With 6 tools, this server is well-scoped for managing Cursor Pro limits and subscriptions. Each tool serves a clear function, such as monitoring usage, checking alerts, and handling subscription tiers, without unnecessary bloat or missing essentials for the domain.
The toolset covers key aspects like monitoring usage, checking limits, and managing subscriptions, but lacks operations for historical data or detailed analytics. Minor gaps exist, such as no tool for listing all services or viewing past alerts, but agents can work around these with the provided tools.