Claude Usage MCP Server
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_claude_usageA | Fetch Claude usage data from the dashboard. Returns daily token usage information. |
| claude_loginA | Open a browser window to authenticate with Claude. Use this if get_claude_usage fails due to authentication. |
| check_claude_authB | Check if the current session is authenticated with Claude. |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: authentication checking, authentication initiation, and usage data retrieval. The descriptions make it easy to differentiate when to use each tool, avoiding misselection.
All tools follow a consistent snake_case pattern with clear verb_noun structure (check_claude_auth, claude_login, get_claude_usage). The naming is predictable and readable throughout the set.
Three tools is borderline thin for a usage monitoring server, as it covers only authentication and data fetching. While functional, additional tools for configuration, historical data, or notifications would make the scope more complete.
The tools cover the core workflow of authentication and usage retrieval well, with no dead ends. A minor gap exists in lacking tools for managing authentication sessions (e.g., logout) or advanced usage analytics, but agents can work around this.