Skip to main content
Glama
Sign In
tokenchit

tokenchit

by iyashjayesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tokenchit

No user-submitted related servers found.

    Related Servers

    • claudeusage

      syk8015
      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

    • codexwatch

      psychofict
      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
      MIT

    • tokenscope

      wartzar-bee
      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

    • Cognitally

      kamanager2012
      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

    This server cannot be deployed

    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation4/5

    get_usage (windowed totals), get_daily_usage (per-day series), and get_recap (year-in-review aggregates) have partially overlapping subject matter, but each description clearly states its scope and output shape. detect_agents is cleanly distinct. Minor risk that an agent asks for a time range and picks get_usage over get_daily_usage.

    Naming Consistency4/5

    Three tools follow a clean get_<noun> snake_case pattern (get_usage, get_daily_usage, get_recap). detect_agents breaks the prefix convention slightly but is still snake_case and readable, so the set is nearly uniform.

    Tool Count4/5

    Four focused tools cover the analytics surface without redundancy. It is on the lean side but each tool earns its place; nothing feels padded or missing at the count level.

    Completeness4/5

    Covers lifetime/window totals, daily series, yearly recap, and agent discovery/diagnostics, which addresses the core questions of a usage-tracking server. Possible gaps like per-project rollups or cross-agent comparison views are not indicated as supported, but no obvious dead end for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Resources