codebase-memory-mcp vs CodeBurn
Which should you use? A side-by-side look at what each one does, who it suits, what it costs, how hard it is to set up, and where each falls short.
Open source · MIT
A local tool that maps your code, docs and infrastructure into a graph so AI coding agents can query it.
Open source · MIT
Local tool that tracks what your AI coding tools spend on tokens, broken down by model, project, and task.
The short answer
Choose codebase-memory-mcp if you need…
- Developers who use an MCP-capable AI coding agent on a large codebase
- Engineers who want to find where a feature lives and how calls connect across files
- Teams that want to estimate which code and tests a change could affect
- People who prefer keeping source analysis on their own machine
Choose CodeBurn if you need…
- Developers who use several AI coding tools and want one view of spending
- People on a Claude subscription who want to see how much of their plan they have used
- Developers who want to find config bloat, such as unused MCP servers or oversized CLAUDE.md files
- Anyone comparing whether a workflow or model change actually lowered cost
Side-by-side
| codebase-memory-mcp | CodeBurn | |
|---|---|---|
| Type | Dev tool | Dev tool |
| Price | Free and open source | Free and open source |
| Licence | MIT | MIT |
| GitHub stars | 48k | 11.7k |
| Setup difficulty | Intermediate | Beginner |
| How you get it | See the README | Install with a package manager |
| Main language | C | TypeScript |
| Last code update | 4 days ago | 5 days ago |
What each one is
codebase-memory-mcp
codebase-memory-mcp is a server that reads a code repository and builds a persistent local knowledge graph of its symbols, files, documentation and infrastructure files. It exposes this graph through the Model Context Protocol (MCP) so an AI coding agent can ask structural questions, such as what calls a function or what depends on a file, instead of reading many files. Indexing and queries run on your own machine, and the README says no hosted service or API key is needed.
CodeBurn
CodeBurn reads the session files that AI coding tools such as Claude Code, Codex, and Cursor write to your disk, then prices every token and shows what you spent. It breaks the total down by tool, model, project, and task, so you can see where a monthly bill actually goes. It runs locally and the README says no account or sign-up is needed.
Best for
codebase-memory-mcp
- Developers who use an MCP-capable AI coding agent on a large codebase
- Engineers who want to find where a feature lives and how calls connect across files
- Teams that want to estimate which code and tests a change could affect
- People who prefer keeping source analysis on their own machine
CodeBurn
- Developers who use several AI coding tools and want one view of spending
- People on a Claude subscription who want to see how much of their plan they have used
- Developers who want to find config bloat, such as unused MCP servers or oversized CLAUDE.md files
- Anyone comparing whether a workflow or model change actually lowered cost
Strengths
codebase-memory-mcp
- Runs locally with no hosted service or API key needed for indexing and queries, per the README
- Ships as a native binary; the README says no Docker or language runtime is required
- Integrates with many agent clients through an installer that writes their configuration
CodeBurn
- Runs locally with no account, and the README says it reads files already on your disk
- Covers many tools and breaks spend down by model, project, git branch, and task
- Optimize and undo commands back up files before changing them, which makes config edits reversible
Not ideal for
codebase-memory-mcp
- Users who want a hosted service or cloud-managed indexing, since the README describes local processing only
- People without an MCP-capable agent or CLI experience, since setup assumes some terminal comfort
- Projects needing change-aware test selection for languages beyond the supported C/C++ harnesses, since Smart CI is described as experimental and limited to supported C/C++ test harnesses
CodeBurn
- People who want a hosted cloud dashboard across a team, since the README describes it as local
- Users of tools outside the supported list, because it only reads the session files of tools it integrates with
- Anyone needing exact billing reconciliation, since the README presents figures as estimates from session data and does not claim they match invoices
Trade-offs
codebase-memory-mcp
- CBM Lens, the visual companion, is in open beta (v0.0.1), and Smart CI is labeled experimental
- Support varies by agent client, so you should check the integration matrix for yours
- The README is truncated, so details such as full language coverage and exact limits are not confirmed here
CodeBurn
- Depends on each tool's session file format, so coverage can change when those tools update
- The README describes several surfaces (desktop app, menu bar, Capacity Dock) that appear to be macOS-focused, and the Windows and Linux feature set is not clearly stated
- README is truncated, so details on privacy of the desktop app and full command list are not verified here
Getting started
codebase-memory-mcp
Install the latest release (macOS / Linux)
curl -fsSL https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/install.sh | bashStart CBM Lens after installation
codebase-memory-mcp daemon start --open --port=9749CodeBurn
Run without installing
npx codeburnInstall globally with npm
npm install -g codeburnFrequently asked questions
What is the difference between codebase-memory-mcp and CodeBurn?
codebase-memory-mcp: A local tool that maps your code, docs and infrastructure into a graph so AI coding agents can query it. CodeBurn: Local tool that tracks what your AI coding tools spend on tokens, broken down by model, project, and task. codebase-memory-mcp suits developers who use an mcp-capable ai coding agent on a large codebase, while CodeBurn suits developers who use several ai coding tools and want one view of spending.
Are codebase-memory-mcp and CodeBurn free?
codebase-memory-mcp: Free and open source. CodeBurn: Free and open source.
Which is easier to set up, codebase-memory-mcp or CodeBurn?
CodeBurn is easier to get started with (rated beginner); codebase-memory-mcp is rated intermediate and usually needs more setup.
Is codebase-memory-mcp or CodeBurn more popular?
codebase-memory-mcp has more GitHub stars (48k) than CodeBurn (11.7k). Popularity isn't the same as fit — check which one matches your use case above.
What are other alternatives to codebase-memory-mcp and CodeBurn?
Other options people compare them with include Trail-code, code-review-graph, Understand Anything, 9Router, planning-with-files.
Keep comparing
Built from our catalogue entries for both products: open-source details come from each project's README (AI-assisted, refreshed weekly) and GitHub data; AI-tool details are editorial. Spotted something wrong? Let us know from either product's page.