Skip to main content
Glama
ryan-knowone

quota-dashboard-mcp

by ryan-knowone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to quota-dashboard-mcp

No user-submitted related servers found.

    Related Servers

    • claude-quota-mcp

      PavolKum
      A
      license
      A
      quality
      B
      maintenance
      Lets an AI agent check its own Claude and Codex usage limits — used percentages and exact reset times for session and weekly windows — so it can plan long-running work around resets instead of dying mid-task. It reads local, credential-free sources by default, always reports which source answered, and ships a hook that pushes quota state into context automatically.
      1
      MIT

    • claudeusage-mcp

      Orellius-Archive
      A
      license
      A
      quality
      Not graded
      maintenance
      Provides real-time visibility into Claude Pro and Max subscription usage limits directly within Claude Code by utilizing local OAuth tokens. It enables users to monitor session and weekly usage across different models and receive alerts regarding rate-limiting status.
      4
      -

    • 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

    • tokenhud

      ZhuoQiuMcgill
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets a coding agent inspect its own account's subscription limit windows, usage, and cost history, and decide whether to pause and sleep until a limit resets rather than failing mid-task. Supports multiple accounts and providers such as Claude Code and Codex.
      14 npm
      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

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: health check, per-provider details, and unified summary. No overlap in functionality.

    Naming Consistency5/5

    All tools follow snake_case and a consistent verb_noun pattern (check_quota_health, get_provider_quota, get_quota_summary).

    Tool Count5/5

    Three tools is appropriate for a quota dashboard, covering health check, per-provider detail, and summary without unnecessary bloat.

    Completeness4/5

    Provides essential read operations for quota monitoring. Minor gap: no tool to update thresholds or configure providers, but the domain appears read-only by design.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources