Cursor Pro Limits MCP Server

get_subscription_info

Retrieve current subscription tier and usage limits for Cursor Pro, including AI service quotas and remaining requests.

Instructions

Get current subscription tier and limits

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_subscription_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/index.ts:381-416 (handler)

The core handler function for the 'get_subscription_info' tool. It fetches the current subscription tier and usage statistics from the CursorLimitsMonitor and formats them into a detailed markdown response including limits, usage percentages, and tier comparisons.

  private async handleGetSubscriptionInfo() {
    const tier = this.monitor.getCurrentTier();
    const stats = this.monitor.getUsageStats();
    
    const content = `
# Subscription Information

## Current Tier: ${tier.toUpperCase()}

## Monthly Limits
- **Sonnet 4.5**: ${stats.quotas.maxSonnet45Requests} requests/month
- **Gemini**: ${stats.quotas.maxGeminiRequests} requests/month
- **GPT-5**: ${stats.quotas.maxGpt5Requests} requests/month
- **Total**: ${stats.quotas.maxTotalRequests} requests/month

## Current Usage
- **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)}%)

## Available Tiers
- **Pro**: 225 Sonnet 4.5, 550 Gemini, 500 GPT-5 (1,275 total)
- **Pro+**: 675 Sonnet 4.5, 1,650 Gemini, 1,500 GPT-5 (3,825 total)
- **Ultra**: 4,500 Sonnet 4.5, 11,000 Gemini, 10,000 GPT-5 (25,500 total)
    `.trim();

    return {
      content: [
        {
          type: 'text',
          text: content,
        },
      ],
    };
  }

src/index.ts:112-119 (registration)
The tool registration entry in the ListTools response, defining the name, description, and input schema (no parameters required).
```
{
  name: 'get_subscription_info',
  description: 'Get current subscription tier and limits',
  inputSchema: {
    type: 'object',
    properties: {},
  },
},
```
src/index.ts:156-158 (registration)
The dispatch case in the CallToolRequest handler that routes calls to 'get_subscription_info' to the specific handler method.
```
case 'get_subscription_info':
  return await this.handleGetSubscriptionInfo();
```
src/index.ts:115-118 (schema)
The input schema for the 'get_subscription_info' tool, which requires no parameters (empty object).
```
inputSchema: {
  type: 'object',
  properties: {},
},
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 10, 2025

TDQS

B3.2/5.0

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 information ('Get'), implying a read-only operation, but doesn't mention potential side effects, authentication requirements, rate limits, or error handling. This leaves significant gaps in understanding how the tool behaves in practice.

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 purpose without any unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate as a basic read operation. However, it lacks details on return values (e.g., format of subscription info), error cases, or dependencies, which could be important for an AI agent to use it correctly in a broader context.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, as there are none to explain. A baseline score of 4 is appropriate since the schema fully covers the lack of parameters.

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 tool's purpose with a specific verb ('Get') and resource ('current subscription tier and limits'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'get_service_usage' or 'get_usage_stats', which might also retrieve subscription-related 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_usage_stats'. It lacks context about prerequisites, such as whether authentication is needed, or exclusions, such as when other tools might be more appropriate.

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

Deploy Server