claude-usage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_USAGE_FORCE_CURL | No | Set to '1' to force using curl instead of fetch |
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 |
|---|---|
| get_usageA | Current Claude subscription usage for every window (5-hour, weekly, weekly-Opus): utilization %, reset time, a forecast of where you'll land at reset, when you'd hit the limit at the current pace, and a velocity recommendation (0-120%; 100 = full speed lands exactly at the limit, <100 = throttle, >100 = headroom to spare). Reuses Claude Code's OAuth session; no API key needed. |
| get_velocityA | Velocity recommendation (0-120%) for one window. 100% = keep going at full speed and you'll land exactly at the limit at reset; <100% = the fraction of your current pace you should slow to; >100% (capped at 120) = you have so much headroom you can't burn through the quota. window: '5h' (rolling 5-hour), 'weekly' (7-day), or 'weekly_opus'. |
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 2 tools
The two tools are mostly distinct: get_usage returns comprehensive usage data for all windows, while get_velocity returns only the velocity recommendation for a single window. However, get_usage already includes velocity recommendations, so an agent might be unclear whether to use get_velocity or extract from get_usage.
Both tools follow a consistent verb_noun pattern (get_usage, get_velocity), making them predictable and easy to understand.
With only 2 tools, the server is on the low side but still reasonable for a focused purpose. The tools cover a narrow domain well without being too sparse.
The server covers the core use case of monitoring Claude usage and velocity recommendations. There are no obvious missing operations for its stated purpose, though it could optionally include a tool for a specific window's full data without velocity.