claude-usage-mcp
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 |
|---|---|
| get_usageA | Report the current user's Claude subscription usage: 5-hour session window, 7-day weekly limit, and any per-model weekly limits, as utilization percentages with reset timestamps. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap. The single get_usage tool has a clearly defined purpose and no competitors.
The tool name get_usage follows the standard verb_noun convention. With a single tool there are no mixed conventions or inconsistent styles.
The server's purpose is narrowly scoped to reporting Claude subscription usage. One tool fully covers this function without unnecessary bloat, making the count appropriate.
For a read-only usage reporting server, get_usage provides all necessary information (session window, weekly limit, model limits, reset timestamps). No create, update, or delete operations are relevant to the domain.