Skip to main content
Glama

Related Servers

Alternatives to claude-usage-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      Reports your Claude subscription usage (5-hour and weekly limits) with a forecast and velocity recommendation, using Claude Code's existing OAuth session without requiring an API key.
      2
      4
      -
    • A
      license
      A
      quality
      Not graded
      maintenance
      Provides real-time visibility into Claude Pro and Max subscription usage limits directly within Claude Code by utilizing local OAuth tokens. It enables users to monitor session and weekly usage across different models and receive alerts regarding rate-limiting status.
      4
      -
    • F
      license
      B
      quality
      Not graded
      maintenance
      Provides comprehensive telemetry and usage analytics for Claude Code sessions, including token usage tracking, cost monitoring, and tool usage patterns. Enables users to monitor their Claude usage with detailed metrics, warnings, and trend analysis.
      12
      -
    • A
      license
      A
      quality
      C
      maintenance
      Real-time Claude.ai subscription awareness for AI coding assistants. Surfaces live utilization, forecasts limits, gates expensive operations, and measures real per-task cost.
      5
      1 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code sessions to check account rate-limit headroom, local token spend, and live session status, with read-only MCP tools for limits, summaries, token usage, and session listing.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Fetches and tracks Claude.ai usage data including session and weekly limits with automated daily logging and persistent session management. It allows users to monitor their usage history directly through Claude Code integrated tools.
      3
      -

    TDQS

    A4.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap. The single get_usage tool has a clearly defined purpose and no competitors.

    Naming Consistency5/5

    The tool name get_usage follows the standard verb_noun convention. With a single tool there are no mixed conventions or inconsistent styles.

    Tool Count5/5

    The server's purpose is narrowly scoped to reporting Claude subscription usage. One tool fully covers this function without unnecessary bloat, making the count appropriate.

    Completeness5/5

    For a read-only usage reporting server, get_usage provides all necessary information (session window, weekly limit, model limits, reset timestamps). No create, update, or delete operations are relevant to the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues