u/deloxalph

Before claudestat:

• No idea how much quota I had left
• No visibility into which tools cost the most
• Couldn't tell if caching was actually helping
• Hit the 5h limit mid-task with no warning

After:

claudestat status
📊 PRO plan
5h  ████████████░░░░░░░░  61%  resets 4:10 AM
Week ██████░░░░░░░░░░░░░░  31%  resets May 18

claudestat top --by cost
web_search    ████████████░░░░░░░░  $0.42  38 calls
read_file     ████████░░░░░░░░░░░░  $0.28  127 calls
bash          ██████░░░░░░░░░░░░░░  $0.21  94 calls

claudestat insights
Cache savings:  $1.24 this week (per-model pricing)
Peak hours:     10am–12pm, 3pm–5pm
Top project:    claudestat ($0.89)

Plus an MCP server — Claude can query its own stats directly.

Install:

npm install -g @statforge/claudestat && claudestat install

Been working on claudestat for a few weeks — a tool that hooks into Claude Code to track token costs, tool calls, quota, and session

efficiency.

This week I shipped the MCP integration. Now instead of switching terminals, you just ask Claude directly and it queries its own stats

live. Screenshots show it in action.

That's it. Hooks and MCP server get registered automatically.

7 MCP tools Claude can call on itself:

- Quota status: 5h cycle percentage, burn rate, reset time

- Current session cost and efficiency score

- Top tools by cost, count, or duration

- Model breakdown: Sonnet vs Haiku vs Opus

- Cache savings and peak hour analysis

- Weekly summary with actionable tip

Also ships with a live dashboard at localhost:7337, a kill switch to auto-block tools when quota gets too high, and a "roast" command for a

brutal breakdown of your worst usage habits.

Zero extra dependencies for the MCP server — pure stdio JSON-RPC, works without the daemon running.

Links in first comment.

Open to feedback — especially what other stats would be useful to expose via MCP.