Skip to main content
Glama
beeltec

context-usage-mcp

by beeltec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to context-usage-mcp

No user-submitted related servers found.

    Related Servers

    • Claude Telemetry MCP

      cordlesssteve
      F
      license
      B
      quality
      Not graded
      maintenance
      Provides comprehensive telemetry and usage analytics for Claude Code sessions, including token usage tracking, cost monitoring, and tool usage patterns. Enables users to monitor their Claude usage with detailed metrics, warnings, and trend analysis.
      12
      -

    • Claude Code Usage

      wheelbarrel00
      A
      license
      Not graded
      quality
      C
      maintenance
      Surface Claude Code token usage, estimated cost, and plan-limit status in any MCP client. Enables agents to query usage data from local logs and Anthropic API.
      MIT

    • contextburn

      arsentev-ai
      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
      52 PyPI
      MIT

    • Token Analyzer MCP

      cordlesssteve
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides intelligent analysis of token usage patterns and optimization recommendations to improve efficiency and reduce costs in Claude Code sessions. Offers real-time analysis, cost metrics, and actionable insights for better context window and tool usage optimization.
      3 npm
      -
    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

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or misselection. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    The single tool name 'get_context_usage' follows a clear verb_noun pattern. Consistency is trivially maintained as there are no other tools to contrast with.

    Tool Count3/5

    The server has only one tool, which feels thin for a typical server but is arguably sufficient for its narrow purpose. It is not trivial, but the count is on the lower end of the acceptable range.

    Completeness3/5

    The tool covers the core raw token usage reporting, but it explicitly lacks percentage or context-window detection, leaving a notable gap for users who need derived insights. The domain is narrowly focused, but the surface is somewhat incomplete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources