Skip to main content
Glama
Sign In
cursor-usage-mcp

cursor-usage-mcp

by udah1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cursor-usage-mcp

No user-submitted related servers found.

    Related Servers

    • preflight

      bulukaka
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides coding agents with pre-flight cost estimation by analyzing local logs to forecast token usage and quota impact before expensive work, exposing tools for remaining quota, per-task cost estimates, and attempt affordability.
      107 npm
      MIT

    • Cursor Pro Limits MCP Server

      mehmetfiskindal
      A
      license
      B
      quality
      D
      maintenance
      Enables real-time monitoring of Cursor Pro usage limits and API quotas across different AI services. Tracks Sonnet 4.5, Gemini, and GPT-5 request usage with alerts when approaching subscription limits.
      6
      2 npm
      MIT

    • Token Runway

      Cpleasance
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to monitor live token consumption and rate-limit windows across providers and assess whether expensive actions are justified before exhausting quotas, with optional budget guardrails.
      2
      MIT

    • genpark-cognitive-load-budget

      Alpha-Park
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables monitoring of running agent loops with token and monetary cost estimation, pruning of verbose thinking chains near limits, and routing sub-tasks between fast/cheap and deep reasoning models. It provides deterministic, MCP-compatible budget optimization for autonomous agents and copilot frameworks.
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: usage reading, auth management, configuration, update handling, and status. Even get_usage and usage_breakdown are well differentiated by weight and intent, with descriptions explicitly stating when to use each.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (get_usage, set_threshold, dismiss_update), but a few deviations exist: usage_breakdown has no verb, and login, logout, and status are single words. This is a minor inconsistency that does not impair readability or prediction.

    Tool Count5/5

    10 tools is well-scoped for a Cursor usage management server. Each tool covers a distinct aspect of the domain without redundancy, and no tool feels superfluous.

    Completeness5/5

    The tool surface covers the full lifecycle: usage retrieval, detailed breakdown, auth options, configuration settings, update management, and an overall status overview. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources