Skip to main content
Glama

Related Servers

Alternatives to codexwatch

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
      A
      quality
      B
      maintenance
      Prices your Claude Code and Codex sessions from the transcripts on disk, shows what each agent cost over any period, and tells you in plain English what would have been cheaper. CLI, Browser UI and MCP server.
      8
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Analyzes Claude Code session token usage and cost locally — where spend actually lands across cache-read, cache-write and output, and what is consuming the context window. Read-only and offline: it parses your own session files and exposes analyze_claude_cost, get_cost_benchmark and tokenscope_share_summary.
      92 npm
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Analyzes local Claude Code logs to measure subscription value, waste, and rate-limit usage, including chat share and current limits, without uploading data.
      4
      MIT

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct slice of Codex usage monitoring: period summary, plan-window status, forensic cost-per-point analysis, session listing, daily time series, and budget status. There is minor overlap between usage_summary, daily, and quota_forensics since all report token/dollar usage, but their descriptions clarify the different granularities and purposes.

    Naming Consistency4/5

    All tools use lowercase snake_case and are noun-based metric/resource names, which is predictable. Minor deviation: some are single words (sessions, daily) while others are compound noun phrases (usage_summary, plan_limits), but the style remains consistent overall.

    Tool Count5/5

    Six tools is well-scoped for a read-only Codex usage and budget monitoring server. Each tool earns its place by covering a different analytical view without excessive granularity.

    Completeness4/5

    The surface covers summaries, daily breakdowns, sessions, plan limits, forensic cost analysis, and budget status, giving strong read coverage of the monitoring domain. A minor gap is the absence of tools to create or edit budgets (only status is exposed), but agents can work around this if budgets are configured elsewhere.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues