claude-quota-mcp
Related Servers
Alternatives to claude-quota-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceLets 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 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseAqualityNot gradedmaintenanceProvides 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-
- AlicenseNot gradedqualityAmaintenanceEnables agents to check remaining Anthropic and OpenAI rate-limit quotas with reset times, plus Hermes Agent token usage, so bots can throttle or stop before hitting limits.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query live 5-hour and 7-day quota limits, per-model allowances, and user plan tiers from the local Google Antigravity 2.0 Language Server. It also forecasts planned task consumption and self-learns from real pre/post measurements, isolating parallel-chat noise.2 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides coding agents with pre-flight cost estimation by analyzing local logs to forecast token usage and quota impact before expensive work, exposing tools for remaining quota, per-task cost estimates, and attempt affordability.276 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between tools. Its purpose (report agent usage limits across providers) is clearly stated and self-contained.
A single tool named quota_status in snake_case noun_status form; a lone name cannot conflict with any other convention. It is readable and predictable.
One tool is thin against the 3-15 guideline, but the server's scope is a narrow read-only status probe, so a single entry point is defensible. No tool feels redundant or bolted on.
The domain is quota/limit reporting, and the tool covers both providers with default 'all' plus fallbacks, which is close to a complete surface for a read-only probe. It lacks historical usage or per-model breakdowns, but these are minor gaps an agent can work around.