head to head · open source

codebase-memory-mcp vs TokenEconomizer

codebase-memory-mcp has 48,837 GitHub stars, 4,058 forks, 573 open issues and last shipped yesterday. TokenEconomizer has 7,683 stars, 525 forks, 41 open issues and last shipped yesterday. codebase-memory-mcp leads on adoption by 536% (48,837 vs 7,683 stars). codebase-memory-mcp is written in C under MIT; TokenEconomizer is written in Python under MIT. codebase-memory-mcp has attracted 8% as many forks as stars, TokenEconomizer 7%. TokenEconomizer was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (claude-code, codex), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

codebase-memory-mcp ★ 49K TokenEconomizer ★ 7.7K category Developer Tools

← all 20902 open source comparisons

Side by side

codebase-memory-mcp TokenEconomizer
GitHub stars ★ 49K ★ 7.7K
License MIT MIT
Written in C Python
Last push 2026-11-19 2026-11-19
Forks ⑂ 4.1K ⑂ 525
Self-hosting Yes Yes
Data ownership Your server Your server

pick codebase-memory-mcp if

  • You weight community size — 49K stars and counting
  • You want the MIT license terms
  • Your stack matches C
  • You value the larger contributor base for long-term maintenance

full codebase-memory-mcp profile →

pick TokenEconomizer if

  • You want the TokenEconomizer feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Python
  • You evaluated both and TokenEconomizer fits your workflow better

full TokenEconomizer profile →

About codebase-memory-mcp

codebase memory mcp: local code intelligence for AI agents via MCP Understand your repository, from source code to the systems around it. codebase memory mcp is an MCP server that connects code, documentation, configuration, and infrastructure in a persistent local knowledge graph. Use it to find an unfamiliar feature, follow a call across services, trace a deployment back to its source, or assess which parts of a project a change could affect. Give your coding agent structural context through Model Context Protocol (MCP), or query the graph directly from the CLI. The MCP server is the core of the project. Its…

read the full codebase-memory-mcp overview →

About TokenEconomizer

TokenEconomizer: Experience Driven Black Box Cost Control for Coding Agents Aaron J. Li 1 , Weijia Xu 2 , Chandan Singh 2 , Zixiao Chen 3 , Jeevana Priya Inala 2 , Charlotte Siska 3 , Acar Tamersoy 3 , Bin Yu 1 , Ion Stoica 1 , Michel Galley 2 , Jianfeng Gao 2 1 UC Berkeley 2 Microsoft Research 3 Microsoft Security Our measurement on SWE Bench tasks: 18.4–30.9% lower mean cost across five agent–model combinations, cheaper in all 30 repository × combination cells, and Pass@1 up in 4 of 5 . Results TokenEconomizer makes coding agents cheaper to run in the repositories you work in often, without changing the agent…

read the full TokenEconomizer overview →

More in Developer Tools

Related comparisons

More Frameworks & Platforms projects

Compare either of these against the rest of the Frameworks & Platforms field.

Frequently asked questions

Is codebase-memory-mcp or TokenEconomizer more popular?

codebase-memory-mcp has 48,837 GitHub stars and TokenEconomizer has 7,683. codebase-memory-mcp has the larger community by that measure.

Are codebase-memory-mcp and TokenEconomizer free?

Both are open source. codebase-memory-mcp is licensed under MIT and TokenEconomizer under MIT. Neither carries a licence fee.

What is the difference between codebase-memory-mcp and TokenEconomizer?

codebase-memory-mcp is written in C and TokenEconomizer in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, codebase-memory-mcp or TokenEconomizer?

Choose codebase-memory-mcp if you want the larger community (48,837 stars) or its MIT licence terms. Choose TokenEconomizer if its feature set, stack or MIT licence fits better. Both are self-hostable.