Skip to main content
Glama
whdrnr2583-cmd

token-meter

by whdrnr2583-cmd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to token-meter

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

    • ai-usage-mcp

      flaviozantut
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for querying AI usage metrics (exact tokens, cost, latency, errors, productivity) from a local SQLite database, enabling charts and analysis in Claude Code and Cursor.
      -

    • Wick MCP

      pranshuguptaa
      F
      license
      A
      quality
      C
      maintenance
      A local MCP server that tracks token usage and costs for Claude Desktop and Claude Code, providing a live dashboard at localhost:6789.
      5
      9 npm
      -

    • LLM Usage & Cost Tracker

      zhaoyue722
      A
      license
      A
      quality
      A
      maintenance
      A local-first, multi-provider cost meter for LLM usage, exposed as MCP tools. Captures every call into a local SQLite ledger and lets any coding agent query spend, compare providers, and get recommendations — no cloud, no account. First-class support for Chinese providers (Qwen, DeepSeek) alongside Anthropic and OpenAI.
      7
      31 PyPI
      5
      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

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct focus: aggregate usage, session listing, per-session tool stats, subagent cost split, and data refresh. There is mild overlap between usage_summary and subagent_costs since both report spend, but the descriptions clearly delineate the scope.

    Naming Consistency4/5

    All names use snake_case and mostly follow a noun-phrase pattern like usage_summary, recent_sessions, and session_tools. refresh_data breaks the pattern as an imperative verb, but the overall naming style is still coherent and predictable.

    Tool Count5/5

    Five tools is a well-scoped count for a focused usage/cost monitoring server. Each tool addresses a distinct analytical need without unnecessary bloat.

    Completeness4/5

    The tool surface covers the core workflow: refresh local data, view aggregate usage, list sessions, inspect per-session tool activity, and analyze subagent costs. Missing advanced capabilities like time-range filtering or raw data export feel like minor gaps rather than fundamental omissions.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources