mcp-token-saver
Related Servers
Alternatives to mcp-token-saver
No user-submitted related servers found.
Related Servers
- 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 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.1,173 npmMIT
- AlicenseAqualityAmaintenanceMartinLoop is the independent governance and financial control layer for AI coding agents. Set hard spend limits, prevent runaway loops, enforce verification, trigger rollback on failure, and generate auditable receipts showing what changed, what it cost, and whether the work passed.24981 npm409Apache 2.0
- FlicenseBqualityNot gradedmaintenanceProvides 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-
- AlicenseNot gradedqualityBmaintenanceLets 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.MIT
- 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
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: cache_stats analyzes cache hit rates, should_proceed makes decisions, usage_delta tracks task costs, usage_forecast predicts limits, and usage_status provides real-time data. No two tools have overlapping functionality.
Three tools follow a 'usage_' prefix pattern (usage_delta, usage_forecast, usage_status), but cache_stats and should_proceed break the pattern. The mix of noun_noun and verb_verb naming creates inconsistency.
Five tools is well-scoped for the token management domain. Each tool serves a necessary function without redundancy or bloat.
The tool set covers all key aspects of token saving: cache analysis, real-time status, forecasting, task cost tracking, and decision guidance. No obvious gaps for the stated purpose.