Skip to main content
Glama
mehmetfiskindal

Cursor Pro Limits MCP Server

get_usage_stats

Monitor Cursor Pro usage statistics and limits for AI services like Sonnet 4.5, Gemini, and GPT-5. Track API quotas and receive alerts when approaching subscription limits.

Instructions

Get current Cursor Pro usage statistics and limits

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_usage_stats'. Retrieves UsageStats from monitor and returns formatted markdown text response.
      private async handleGetUsageStats() {
        const stats = this.monitor.getUsageStats();
    
        const content = `
    # Cursor Pro Usage Statistics
    
    ## Subscription Tier: ${stats.quotas.tier.toUpperCase()}
    
    ## Current Usage (Monthly)
    - **Sonnet 4.5**: ${stats.limits.sonnet45Requests}/${stats.quotas.maxSonnet45Requests} (${stats.usagePercentages.sonnet45.toFixed(1)}%)
    - **Gemini**: ${stats.limits.geminiRequests}/${stats.quotas.maxGeminiRequests} (${stats.usagePercentages.gemini.toFixed(1)}%)
    - **GPT-5**: ${stats.limits.gpt5Requests}/${stats.quotas.maxGpt5Requests} (${stats.usagePercentages.gpt5.toFixed(1)}%)
    - **Total**: ${stats.limits.totalRequests}/${stats.quotas.maxTotalRequests} (${stats.usagePercentages.total.toFixed(1)}%)
    
    ## Remaining Requests (This Month)
    - **Sonnet 4.5**: ${stats.remaining.sonnet45}
    - **Gemini**: ${stats.remaining.gemini}
    - **GPT-5**: ${stats.remaining.gpt5}
    - **Total**: ${stats.remaining.total}
    
    ## Last Updated
    ${stats.limits.lastUpdated.toISOString()}
        `.trim();
    
        return {
          content: [
            {
              type: 'text',
              text: content,
            },
          ],
        };
      }
  • src/index.ts:41-47 (registration)
    Registration of the 'get_usage_stats' tool in the ListTools response, including name, description, and input schema.
      name: 'get_usage_stats',
      description: 'Get current Cursor Pro usage statistics and limits',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Dispatch handler in CallToolRequestSchema switch statement that routes to handleGetUsageStats.
    case 'get_usage_stats':
      return await this.handleGetUsageStats();
  • Input schema for the tool: empty object (no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • Core helper method that computes comprehensive UsageStats including limits, quotas, percentages, and remaining requests.
    public getUsageStats(): UsageStats {
      const usagePercentages = {
        sonnet45: this.calculatePercentage(
          this.limits.sonnet45Requests,
          this.quotas.maxSonnet45Requests
        ),
        gemini: this.calculatePercentage(
          this.limits.geminiRequests,
          this.quotas.maxGeminiRequests
        ),
        gpt5: this.calculatePercentage(
          this.limits.gpt5Requests,
          this.quotas.maxGpt5Requests
        ),
        total: this.calculatePercentage(
          this.limits.totalRequests,
          this.quotas.maxTotalRequests
        ),
      };
    
      const remaining = {
        sonnet45: Math.max(
          0,
          this.quotas.maxSonnet45Requests - this.limits.sonnet45Requests
        ),
        gemini: Math.max(
          0,
          this.quotas.maxGeminiRequests - this.limits.geminiRequests
        ),
        gpt5: Math.max(0, this.quotas.maxGpt5Requests - this.limits.gpt5Requests),
        total: Math.max(
          0,
          this.quotas.maxTotalRequests - this.limits.totalRequests
        ),
      };
    
      return {
        limits: { ...this.limits },
        quotas: { ...this.quotas },
        usagePercentages,
        remaining,
      };
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't mention any constraints like authentication requirements, rate limits, or whether the data is real-time or cached. This leaves significant gaps for a tool that likely accesses sensitive usage information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's function without any fluff. It's front-loaded with the core action and resource, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't specify what 'usage statistics and limits' include (e.g., API calls, storage, user counts) or the format of the response, which is critical for an agent to use this tool effectively in a context with sibling tools that might overlap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose. A baseline of 4 is applied since the schema fully handles the parameter aspect.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'current Cursor Pro usage statistics and limits', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_service_usage' or 'get_subscription_info', which likely provide related but different information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'get_service_usage' or 'get_subscription_info'. It lacks context about what specific statistics or limits are included, leaving the agent to guess based on tool names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mehmetfiskindal/cursor-pro-limits-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server