Skip to main content
Glama
mvacaporale

Claude Usage MCP Server

by mvacaporale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Claude Usage MCP Server

No user-submitted related servers found.

    Related Servers

    • claudeusage-mcp

      Orellius-Archive
      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
      -

    • work-tracker

      dud0880
      A
      license
      Not graded
      quality
      C
      maintenance
      Automatically tracks AI-assisted work sessions, code changes, and commands in Claude Code or Codex CLI, and provides daily stats, weekly reports, and data export through MCP tools.
      23 npm
      MIT

    • Claude Telemetry MCP

      cordlesssteve
      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
      -

    • Claude Session MCP

      TimEvans
      A
      license
      A
      quality
      D
      maintenance
      Provides Claude Code with programmatic session awareness to track context usage, session history, and task progress. It enables intelligent context reset recommendations and automatic synchronization of project planning documentation.
      5
      MIT

    • claude-usage-mcp

      NG-Bullseye
      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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: authentication checking, authentication initiation, and usage data retrieval. The descriptions make it easy to differentiate when to use each tool, avoiding misselection.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with clear verb_noun structure (check_claude_auth, claude_login, get_claude_usage). The naming is predictable and readable throughout the set.

    Tool Count3/5

    Three tools is borderline thin for a usage monitoring server, as it covers only authentication and data fetching. While functional, additional tools for configuration, historical data, or notifications would make the scope more complete.

    Completeness4/5

    The tools cover the core workflow of authentication and usage retrieval well, with no dead ends. A minor gap exists in lacking tools for managing authentication sessions (e.g., logout) or advanced usage analytics, but agents can work around this.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources