claudestat-mcp-bundle
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_quota_statusB | Get current Claude Code quota status: 5h cycle usage %, plan type, weekly hours per model, and burn rate (tokens/min) |
| get_current_sessionA | Get details about the most recent Claude Code session: cost, tokens, efficiency score, and loops detected |
| get_session_statsA | Get aggregated session statistics for the last N days: session count, total cost, total tokens, loops, and average efficiency |
| get_top_toolsB | Get the top 10 most used tools by cost, call count, or duration in the last N days |
| get_usage_insightsB | Get unique usage insights not available in /usage: cost per project, cache savings, output/input ratio, efficiency trend, and peak hours |
| get_model_breakdownB | Get cost and session count broken down by Claude model (Sonnet, Haiku, Opus) for the last N days |
| get_weekly_insightB | Get the weekly usage summary with an actionable tip (same as claudestat weekly command) |
| get_context_statusA | Get current context window usage for the latest session: used tokens, window size, percentage, and model |
| get_daily_summaryB | Get today's usage summary vs yesterday and 7-day personal average: cost, sessions, tokens, top tool, and weekly pace |
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 9 tools
Each tool targets a distinct aspect of Claude Code usage (quota, session, context, model breakdown, etc.) with clear descriptions, eliminating ambiguity.
All tools use a consistent 'get_' prefix followed by a descriptive noun phrase in snake_case, e.g., get_quota_status, get_current_session.
9 tools is an appropriate size for a usage analytics server, covering various queries without being excessive or insufficient.
The tool set covers all major usage analytics: quota, session details, aggregated stats, top tools, insights, model breakdown, context, daily and weekly summaries, with no obvious gaps.