Skip to main content
Glama
wn01011

llm-token-tracker

by wn01011
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to llm-token-tracker

No user-submitted related servers found.

    Related Servers

    • ai-usage-mcp

      MohitBansal321
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local-first tracking of AI token usage and costs from Claude Code and OpenCode, answering queries about tokens, models, sessions, and cost through MCP tools and a CLI, with no network calls.
      321 npm
      1
      MIT

    • agentfit-mcp

      MukundaKatta
      A
      license
      A
      quality
      D
      maintenance
      Lets Claude Desktop, Cursor, Cline, Windsurf, Zed, or any other MCP client estimate token counts and fit a chat history into a model's context budget on demand.
      3
      35 npm
      1
      MIT

    • Tokenomics MCP

      JonThads
      A
      license
      A
      quality
      C
      maintenance
      Counts LLM prompt tokens and estimates API costs across OpenAI and Anthropic models directly inside MCP-compatible chat clients. Supports exact tokenization for OpenAI models and fallback approximation for Claude when no API key is present.
      4
      MIT

    • MCP TokenSage

      quangminh1212
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables token counting, usage tracking, and cost calculation for LLM APIs, with a proxy server mode to automatically intercept and monitor API requests from clients like Cursor and Windsurf.
      15 npm
      1
      MIT
    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

    B3.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have distinct purposes, but get_current_session and get_usage could be confused as both retrieve usage data, though their descriptions differentiate them slightly (session-specific vs. summary). The other tools (clear_usage, compare_costs, get_exchange_rate, track_usage) are clearly distinct.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., clear_usage, compare_costs, get_current_session). There are no deviations in naming style, making them predictable and readable.

    Tool Count5/5

    With 6 tools, the count is well-scoped for tracking LLM token usage and costs. Each tool serves a specific function in this domain, such as tracking, retrieving, clearing, and comparing data, without being excessive or insufficient.

    Completeness3/5

    The toolset covers core operations like tracking, retrieving, and clearing usage, but lacks update or delete capabilities for specific entries, which might be needed for error correction. The inclusion of get_exchange_rate is useful but slightly tangential to the main purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources