claude-budget-mcp
Related Servers
Alternatives to claude-budget-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables retrieving real Claude subscription usage statistics, including the 5-hour session window, weekly limit, and per-model limits, from the same endpoint Claude Code uses.110 npmMIT
- FlicenseAqualityCmaintenanceReports your Claude subscription usage (5-hour and weekly limits) with a forecast and velocity recommendation, using Claude Code's existing OAuth session without requiring an API key.24-
- 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 gradedqualityBmaintenanceGives the model visibility into the same 5-hour session, weekly, and per-model usage percentages shown in Claude Code, along with reset times. It also lets a project cap how much of the weekly limit may be spent via start/check/end budget tools that report OK, LOW, or OVER_BUDGET.1MIT
- AlicenseNot gradedqualityBmaintenanceLets 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.MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code sessions to check account rate-limit headroom, local token spend, and live session status, with read-only MCP tools for limits, summaries, token usage, and session listing.MIT
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or misselection. The single tool's purpose is clear and distinct.
The tool name 'get_budget' follows a clear verb_noun snake_case convention. With only one tool, consistency is trivially maintained.
One tool is slightly under the typical 3-15 range, but it perfectly matches the narrow read-only scope of fetching a single usage endpoint. No additional tools are needed for the stated purpose.
The tool covers the core read operation for subscription usage limits, including session and weekly windows with detailed fields. However, it lacks any write or management operations for budgets or alerts, which the server name might imply.