mcpField
C
claude-code-usage

claude-code-usage

Local
github.com/wheelbarrel00Data & Analytics0Updated 18w ago

About claude-code-usage

claude-code-usage is an MCP server for Claude Code users who want usage and cost data from local logs and Anthropic's usage API. It provides on-demand summaries and breakdowns without a persistent status display.

Key features

  1. 01Reports token usage and estimated cost
  2. 02Shows plan-limit utilization and reset times
  3. 03Projects usage pace from recent burn rate
  4. 04Shows current context-window fill
  5. 05Breaks usage down by model, project, session, or branch
  6. 06Summarizes daily and monthly usage

Use cases

  1. 01Checking today's Claude Code usage and cost
  2. 02Reviewing plan-limit status and reset timing
  3. 03Comparing usage across projects or models

MCP support

It exposes tools for usage summaries and breakdowns to MCP clients. Data comes from Claude Code's local logs and Anthropic's usage API.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"wheelbarrel00-claude-code-usage": {
"command": "npx",
"args": [
"-y",
"claude-code-usage-mcp"
]
}
}
}
Run commandnpx -y claude-code-usage-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmclaude-code-usage-mcp0.1.0

Tools

2

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project README

Claude Code Usage

npm version MCP Registry License: MIT

An MCP server that surfaces your Claude Code token usage, estimated cost, and plan-limit status in any MCP client (Zed, Claude Desktop, Cursor, and others). It reads Claude Code's own logs (~/.claude/projects/**/*.jsonl) and Anthropic's usage API, then exposes the data as tools the agent can call.

Published on npm as claude-code-usage-mcp and in the official MCP registry as io.github.wheelbarrel00/claude-code-usage.

What you get

Two tools:

  • get_claude_usage — today's cost and tokens, 5-hour and weekly plan-limit utilization (with reset times and a pace projection), recent burn rate, current context-window fill, and pay-as-you-go extra usage.
  • get_usage_breakdown — usage grouped by model, project, session, or git branch, or over time (daily this month / monthly all-time).

Ask the agent things like "what's my Claude usage right now?" or "break down my Claude spend by project this month." MCP tools are queried on demand — there's no persistent status-bar display.

Install

npx -y claude-code-usage-mcp

Register it with your client. For Zed (settings.json):

{
  "context_servers": {
    "claude-code-usage": {
      "command": "npx",
      "args": ["-y", "claude-code-usage-mcp"]
    }
  }
}

For Claude Desktop (claude_desktop_config.json), use the same command under "mcpServers" instead of "context_servers".

Requirements

An authenticated Claude Code install — the server reads ~/.claude/.credentials.json and ~/.claude/projects, the same files the CLI writes.

Configuration

Optional environment variables:

VariableDefaultMeaning
CCU_CURRENCYUSDISO currency code for cost formatting.
CCU_DECIMALS2Decimal places for cost figures.
CCU_USE_LIVE_APItrueFetch live limits from Anthropic; falls back to the on-disk cache.
CCU_LIVE_MIN_INTERVAL_SECONDS180Minimum seconds between live usage requests.
CCU_BURN_WINDOW_MINUTES15Trailing window for the burn-rate calculation.
CCU_PROJECT_GROUPINGgitgit, folder, or flat grouping for the project breakdown.
CLAUDE_CONFIG_DIR~/.claudeOverride the Claude Code config directory.

How it works

Live plan limits come from api.anthropic.com/api/oauth/usage using the OAuth token already on disk; the access token is refreshed in memory only, so a running Claude Code session is never logged out. Token and cost figures are parsed from the local session logs.

Repository layout

  • mcp-server/ — the MCP server (TypeScript, bundled to dist/server.mjs).
  • extension.toml, Cargo.toml, src/lib.rs — a self-contained Zed extension that embeds and launches the server (an alternative to the npx install above).

Build from source

cd mcp-server
npm install
npm run build      # bundles to dist/server.mjs
node dist/server.mjs --selftest
Zed extension (self-contained, no npm needed)

The Zed extension embeds the bundled server and launches it with Zed's own Node. Build the server first, install rustup and the WebAssembly target (rustup target add wasm32-wasip1), then in Zed open Extensions → Install Dev Extension and select this repository's root folder.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.