Skip to main content
Glama

Related Servers

Alternatives to agy-token-monitor

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides real-time rate-limit and context budget awareness to Claude Code, enabling it to plan tasks that fit within its constraints and defer work when needed.
      8 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query live 5-hour and 7-day quota limits, per-model allowances, and user plan tiers from the local Google Antigravity 2.0 Language Server. It also forecasts planned task consumption and self-learns from real pre/post measurements, isolating parallel-chat noise.
      3 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that lets an agent hand real coding tasks to the signed-in Google Antigravity CLI, with background runs, follow-ups, live status, cancellation, independently collected change evidence, execution traces, model listing, login, and quota-based account rotation. It requires no API key, relying instead on the existing Antigravity login and optionally exposing agy models through a bundled local model gateway.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that acts as a context-aware code retrieval broker for AI coding agents, enforcing backpressure and token budgeting to prevent context window overflow.
      4
      43 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have reasonably clear boundaries: quota (account-level), session usage (conversation-level), and a summary that aggregates both. The summary tool overlaps by design with the other two, which could tempt an agent to skip the granular tools, but the descriptions make the distinction explicit.

    Naming Consistency5/5

    All three tools follow the same verb_noun snake_case pattern with a consistent 'get_' prefix (get_account_quota, get_session_token_usage, get_token_awareness_summary). The names are predictable and immediately map to their outputs.

    Tool Count4/5

    Three tools is on the lean side but appropriate for a narrowly scoped monitoring server covering two distinct metrics plus an aggregate. Nothing feels superfluous, though the summary tool is arguably a convenience layer rather than an independent capability.

    Completeness3/5

    The core read path (quota, session consumption, combined health) is covered, but a monitoring domain typically also implies historical trends, threshold/alert configuration, or reset-time details, none of which exist here. It is read-only with no lifecycle operations, which is acceptable for a monitor but leaves notable gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues