Skip to main content
Glama

Related Servers

Alternatives to Tokmeter

No user-submitted related servers found.

    Related Servers

    • 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
      B
      quality
      B
      maintenance
      Lets a coding agent inspect its own run efficiency mid-session from local Claude Code transcripts, exposing the share of paid tokens that became model output versus context re-reading. Ships two stdio tools — one returning the shares as structured data and one returning the full cost-weighted report — with no network calls.
      2
      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
    • 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.
      54 npm
      4
      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

    TDQS

    A3.8/5.0

    Scored across 22 tools

    Disambiguation4/5

    The descriptions are unusually good at disambiguating each other, explicitly routing agents (e.g. totals → tokmeter_pulse, per-model → tokmeter_models, caching dollars → tokmeter_cache_efficiency). Some residual overlap remains among the analytical views — leaderboard vs. compare vs. models, efficiency vs. cache_efficiency, budget vs. budget_alert, and model_advisor vs. cost_optimization_tips — but the cross-references keep misselection unlikely.

    Naming Consistency4/5

    All 22 tools share the tokmeter_ prefix and snake_case, giving a predictable, readable namespace. The style is topic-noun oriented (providers, projects, heatmap, timeline) rather than a strict verb_noun pattern, and a few names are verbs (search, compare, export), but the convention is internally consistent.

    Tool Count3/5

    22 tools is on the heavy side for a usage-analytics server, and several are narrow slices of the same data (streaks, heatmap, timeline, digest, pulse). Each has a plausible use, but the surface feels broader than strictly necessary and invites choice paralysis.

    Completeness4/5

    Coverage of the analytics domain is strong: overview, per-provider/project/model rollups, timeline, heatmap, forecast, anomaly, budgets, efficiency, caching, search, export, and cleanup preview with backup listing. Gaps are minor and deliberate — cleanup execution is not exposed over MCP (documented workaround) and there is no backup restore or settings/pricing-override tool.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data