Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Claude Code token usage, cost, and plan limits from local logs and Anthropic's usage API.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"claude-code-usage": {
"command": "npx",
"args": [
"-y",
"claude-code-usage-mcp"
]
}
}
}Run this in your terminal
claude mcp add claude-code-usage -- npx -y claude-code-usage-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"claude-code-usage": {
"command": "npx",
"args": [
"-y",
"claude-code-usage-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"claude-code-usage": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"claude-code-usage-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account wheelbarrel00, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
Two tools:
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.
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".
An authenticated Claude Code install — the server reads ~/.claude/.credentials.json and ~/.claude/projects, the same files the CLI writes.
Optional environment variables:
| Variable | Default | Meaning |
|---|---|---|
CCU_CURRENCY | USD | ISO currency code for cost formatting. |
CCU_DECIMALS | 2 | Decimal places for cost figures. |
CCU_USE_LIVE_API | true | Fetch live limits from Anthropic; falls back to the on-disk cache. |
CCU_LIVE_MIN_INTERVAL_SECONDS | 180 | Minimum seconds between live usage requests. |
CCU_BURN_WINDOW_MINUTES | 15 | Trailing window for the burn-rate calculation. |
CCU_PROJECT_GROUPING | git | git, folder, or flat grouping for the project breakdown. |
CLAUDE_CONFIG_DIR | ~/.claude | Override the Claude Code config directory. |
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.
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).cd mcp-server
npm install npm run build # bundles to dist/server.mjs node dist/server.mjs --selftest
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.
MIT