CodeBurn MCP server

The problem

Your bill gives you a month total. It does not break that down by project, by model or by task, and it does not show which part of it was wasted.

Claude Code, Codex, Cursor and the rest each write a session file every time you use them, and those files hold every token and every model call. CodeBurn reads those files and produces the breakdown.

Sixty seconds

npx codeburn

There is no account and no sign-up. CodeBurn looks in the folders your tools already write to, prices every token, and prints what you spent.

Under the total are the tables: cost by tool, by model, by project and by task. Task means what the agent was doing, such as coding, debugging or planning, worked out from the session itself.

Arrow keys move the period, from today out to your whole history. Press p to switch between tools. Press q to quit.

See it

The desktop app is the same data with room to move around in. It opens on today: what you have spent, what the month is on pace to cost, and the last thirty days day by day.

One click from the clock, the menu bar popover shows the short version of that page. The Capacity Dock adds a ring per provider at the screen edge. Hover a ring and a glance card tells you what is running right now and which limits are filling up.

All four read the same files on your disk, so they show the same numbers, allowing for when each one last refreshed.

The same numbers are in your browser with codeburn web, and in the terminal with codeburn.

Understand it

Every number in the app is clickable. Click today's total and you land on Sessions, one row per session with its project, its model, its tokens and its cost. Click a row and you get the turns inside it, so you can see which part of the work was expensive.

On the Spend page the same money is cut four ways, by project, by git branch, by model and by task. The branch view adds up every session you ran while you were on that branch, so you get the cost of a feature.

Compare periods puts two date ranges side by side and shows the difference. Use it after you change something, a model or a workflow or a prompt, to find out whether the change actually cost less.

The Pull requests page matches spend against the pull requests your sessions recorded, so you can see which spend shipped (Yield).

Fix it

codeburn optimize

Optimize reads your sessions and your config, then lists what costs tokens without earning them. A file the agent re-reads on every turn. An MCP server you installed months ago and never call. A CLAUDE.md that grew long enough to ride along in every single request.

Each finding comes with a grade, the fix, and what that fix should save you over the period it scanned.

CodeBurn can make the config changes for you, and take them back:

codeburn optimize --apply   # review and apply
codeburn act undo --last    # put it back

Files are backed up before they are changed, and you see the change before anything is applied. A few days later, codeburn act report checks what each fix promised against what your sessions actually did, including the fixes that changed nothing.

Stay ahead

codeburn plan set claude-max   # the plan you pay for
codeburn quota                 # how much of it is left
codeburn guard install         # spending caps for Claude Code

Tell CodeBurn which subscription you pay for and it stops showing only what you spent. It shows how much of the plan you have used, and whether the month is on pace to run past it.

codeburn quota reads the live limits out of the tools you are already signed in to. That is where the five-hour and weekly windows come from. Check it before a long run.

Guard is opt-in and local. codeburn guard install adds Claude Code hooks that warn a session once it passes $5 and stop it at $15, and do the same for a tool call stuck in a loop or a failing command retried over and over. All the limits are yours to change, codeburn guard status shows where the hooks live, and codeburn guard uninstall takes them out again.

Always in view

Today's spend sits in the macOS menu bar, beside the clock. Click it and the popover opens on the same figures as the app, with today, the period switcher, the trend and the per-model breakdown.

The Capacity Dock docks a thin rail to any edge of your screen, with one ring per provider showing how much of that plan is left. It shows what is left before you start a run, not after.

Turn either on from the desktop app's Plugins page in one click, or from the command line:

codeburn menubar

On Linux the same view lives in the top panel, as a GNOME Shell extension.

The desktop app runs on Windows. Install it from the Microsoft Store, which is the recommended way and keeps itself up to date, or take the direct installer. The Windows tray app shows today's cost next to the clock, the same way the macOS menu bar does, and clicking it opens the same popover. The Capacity Dock is there too, from the tray menu or the app's Plugins page. If you run your agents inside WSL, CodeBurn reads the distro's home directory as well as your Windows profile, so sessions you ran in Linux are counted without you installing anything twice.

Setup for all three platforms, including WSL, is in Menu bar and tray.

Inside your agent

In Claude Code, install the plugin. It sets up the MCP server below and adds /codeburn:cost, which summarizes today's spend:

/plugin install codeburn --marketplace getagentseal/codeburn

Or register only the MCP server:

claude mcp add codeburn -- npx -y codeburn mcp

That registers a local MCP server over stdio. Your agent can then answer "where did my tokens go this week" or "what should I change to spend less" without you leaving the conversation.

It reads the same files on disk that the CLI reads. The server answers from that local data and makes no network call of its own, and project names are pseudonymized unless the agent asks for them.

Works with 42 tools

CodeBurn detects the tools you already use. There is nothing to configure and no folder to point it at. If a tool is installed and has sessions on disk, it shows up. Each logo links to that tool's page.

Each page lists where that tool keeps its data, the format it uses, and the quirks CodeBurn works around.

Amp · Antigravity · Claude Code · Cline · Cline CLI · Codebuff · Codex · CodeWhale · Command Code · Copilot · Crush · Cursor · Cursor Agent · DeepSeek Harness · Devin · Droid · Forge · Gemini CLI · Goose · Grok Bot · Grok Build · Hermes Agent · IBM Bob · KiloCode · Kimi · Kimi Code · Kiro · LingTai TUI · Mistral Vibe · Mux · OMP · Open Design · OpenClaude · OpenClaw · OpenCode · Pi · Qwen · Quick Desktop · Warp · ZCode · Zed · Zerostack

CodeBurn also reads the Vercel AI Gateway reporting API, which is a gateway rather than a tool, so its spend is shown on its own row and left out of your totals by default.

If several of these have sessions on disk, press p in the dashboard to move between them. A path that has changed is worth an issue. Adding a tool is a single file: see src/providers/codex.ts.

Private by design

CodeBurn reads files that are already on your disk. There is no account, no API key and no proxy in front of your agent.

Your prompts, your code and your project names stay on your computer. CodeBurn does not sit between you and your agent, so if it stopped working tomorrow your tools would not notice.

Prices come from LiteLLM and refresh once a day.

Everything that does leave your machine is listed in Privacy.