mcp-token-saver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| usage_statusA | Fetch real-time Claude.ai subscription usage (5h session and 7d weekly utilization, reset times, extra credits) from the same endpoint Claude Code's IDE bar uses. Reads OAuth token from ~/.claude/.credentials.json. Auto-logs to history. |
| usage_forecastA | Compute burn rate and ETA to 100% based on logged usage history. Tells you whether you'll hit the limit before the next reset. |
| should_proceedA | Decide whether to proceed with a task given current usage. Returns proceed/downgrade/abort. Call BEFORE producing large responses, doing huge file reads, or starting expensive operations. |
| usage_deltaA | Track real cost of a single task. action='mark' saves baseline, action='measure' returns delta in % of session/weekly used. Replaces theoretical cost estimates with real ones. |
| cache_statsA | Compute Anthropic prompt cache hit rate from the latest Claude Code session log. Low hit rate signals wasted tokens — usually caused by reordering tools or system prompt mid-session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.