Skip to main content
Glama
mehmetfiskindal

Cursor Pro Limits MCP Server

set_subscription_tier

Configure subscription levels (pro, pro-plus, ultra) to manage AI service usage limits and quotas within the Cursor Pro monitoring system.

Instructions

Set the subscription tier (pro, pro-plus, ultra)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierYesSubscription tier

Implementation Reference

  • Executes the set_subscription_tier tool: validates tier, updates monitor tier, returns markdown with new limits and usage stats.
      private async handleSetSubscriptionTier(args: { tier: string }) {
        const { tier } = args;
        
        if (!['pro', 'pro-plus', 'ultra'].includes(tier)) {
          throw new Error('Invalid tier. Must be one of: pro, pro-plus, ultra');
        }
    
        this.monitor.updateTier(tier as SubscriptionTier);
    
        const stats = this.monitor.getUsageStats();
        const content = `
    # Subscription Tier Updated
    
    ## New 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)}%)
        `.trim();
    
        return {
          content: [
            {
              type: 'text',
              text: content,
            },
          ],
        };
      }
  • src/index.ts:97-111 (registration)
    Registers the tool in ListToolsRequestHandler with name, description, and input schema.
    {
      name: 'set_subscription_tier',
      description: 'Set the subscription tier (pro, pro-plus, ultra)',
      inputSchema: {
        type: 'object',
        properties: {
          tier: {
            type: 'string',
            enum: ['pro', 'pro-plus', 'ultra'],
            description: 'Subscription tier',
          },
        },
        required: ['tier'],
      },
    },
  • src/index.ts:151-154 (registration)
    Dispatches tool calls for set_subscription_tier to the handler in CallToolRequestHandler.
    case 'set_subscription_tier':
      return await this.handleSetSubscriptionTier(
        args as { tier: string }
      );
  • Type definition for valid subscription tiers used in handler validation and monitor.
    export type SubscriptionTier = 'pro' | 'pro-plus' | 'ultra';
  • Core helper called by handler to update quotas for the new tier and notify observers.
    public updateTier(tier: SubscriptionTier): void {
      this.quotas = this.getQuotasForTier(tier);
      this.notifyCallbacks();
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose if this is a mutation requiring admin rights, if it's reversible, what side effects occur, or error conditions. For a write operation with zero annotation coverage, this is insufficient.

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 with zero waste. It's front-loaded with the core action and includes all necessary tier values without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on permissions, side effects, return values, or error handling. Given the complexity of changing subscription tiers, more context is needed for safe and effective use.

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

Parameters3/5

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

Schema description coverage is 100%, with the parameter 'tier' fully documented in the schema including its enum values. The description adds no additional parameter semantics beyond restating the tier options, so it meets the baseline of 3 where the schema does the heavy lifting.

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 action ('Set') and the resource ('subscription tier'), with specific tier values listed. It distinguishes from siblings like 'get_subscription_info' (read vs write) but doesn't explicitly differentiate from other write operations like 'update_usage'.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, permissions needed, or when not to use it (e.g., vs 'update_usage'). It's a basic functional statement without contextual usage advice.

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