Skip to main content
Glama

Related Servers

Alternatives to claudeusage-mcp

No user-submitted related servers found.

    Related Servers

      TDQS

      A4/5.0

      Scored across 4 tools

      Disambiguation5/5

      Each tool has a clearly distinct purpose with no overlap: check_rate_status monitors rate limiting status, get_session_usage shows 5-hour session data, get_usage provides a comprehensive subscription dashboard, and get_weekly_limits focuses specifically on weekly model breakdowns. The descriptions make it easy to distinguish between session-based, weekly, and rate limit monitoring functions.

      Naming Consistency5/5

      All tools follow a consistent verb_noun pattern with 'get_' or 'check_' prefixes: check_rate_status, get_session_usage, get_usage, and get_weekly_limits. The naming is perfectly uniform and predictable, making it easy for agents to understand what each tool does based on its name alone.

      Tool Count5/5

      Four tools is ideal for this monitoring-focused server - it covers all essential usage tracking aspects without being overwhelming. Each tool serves a distinct monitoring function (rate limits, session usage, overall usage, weekly limits), and there are no redundant or missing tools for the server's purpose.

      Completeness5/5

      The tool set provides complete coverage for Claude usage monitoring: it covers rate limiting status, session-level usage, subscription-level usage, and weekly model breakdowns. There are no obvious gaps - agents can monitor all relevant usage dimensions from different time perspectives (real-time, 5-hour sessions, weekly cycles) and get both detailed breakdowns and summary views.