Skip to main content
Glama

Related Servers

Alternatives to Gauge

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Reports OpenAI Codex token use, API-equivalent cost and the ChatGPT plan's 5-hour and weekly limits from Codex's local session logs. Tools for usage summaries, plan limits, quota forensics, sessions, daily totals and budgets.
      6
      101 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents such as Claude Code, Cursor, Codex, and OpenCode to query local token usage, costs, quotas, projects, and models through six strictly read-only tools. All data stays on the local machine, drawn from passively parsed session logs rather than uploaded telemetry.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables reading locally recorded Codex execution traces — reconstructed requests, nested tool calls and their results, compaction history, and generation timing — browsed alongside the current conversation through timeline, ledger, and inspector views. Also lets users register additional trace directories and inspect large recordings incrementally without any upload or remote service.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to view average token throughput, output and reasoning token counts, and recent speed trends for local Codex Desktop conversations through a session panel without modifying the client.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Reads the Claude Code, Codex and OpenCode usage logs already on your machine and reports token totals, per-day and per-hour activity, a per-agent and per-model breakdown, and a year-in-review recap. It makes no network request at all — a test fails if any source file in the package can open a socket.
      4
      14
      MIT

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct operation: opening/refreshing the dashboard, listing chats, fetching per-call history, and fetching aggregate reuse metrics. The main potential confusion is between get_cache_history and get_cache_summary, both of which return per-chat token/cache data, though the descriptions differentiate per-prompt history vs whole-chat/latest-call reuse.

    Naming Consistency5/5

    All five tools follow a consistent snake_case verb_noun pattern (show_, refresh_, list_, get_ + object). The verbs accurately reflect the read/open semantics of each tool.

    Tool Count4/5

    Five tools is a tight, well-scoped surface for a cache dashboard domain. show_cache_dashboard and refresh_cache_dashboard are close enough that a single parameterized tool could suffice, but the split is defensible since refresh explicitly avoids a model call.

    Completeness4/5

    The surface covers the core read-only lifecycle: open the dashboard, refresh it, enumerate chats, and inspect both detailed history and aggregated summaries. Minor gaps exist around cache management actions (e.g. clearing or exporting data) and credit-level breakdowns, but agents can work around these for inspection tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues