codebase-memory-mcp vs memtrace-public
codebase-memory-mcp: codebase-memory-mcp is a structural analysis backend that indexes codebases into a persistent knowledge graph, drastically reducing token usage for code exploration by providing precise structural results. It integrates with AI assistants like Claude Code, offering advanced capabilities such as call graph tracing, architecture overviews, and dead code detection.; memtrace-public: Memtrace is a persistent memory layer for coding agents. It builds a bi-temporal, episodic, structural knowledge graph from your codebase's AST, enabling agents to remember and reason about code structure, evolution, and dependencies. It runs entirely locally, indexing code in seconds and providing sub-millisecond query latency.
TL;DR
- Your agent burns tokens searching a medium or large codebase: one graph query replaces many grep and read steps, according to the README.
- You want everything local: a single static binary with no runtime dependencies or API keys.
- You work in many languages and with several coding agents, which the installer configures automatically.
- You do not want an installer to edit your agents' config files and add hooks; the README offers --skip-config to install only the binary.
- You need project decisions and conventions rather than code structure; a scaffold such as mex is closer.
- You are cautious about unsigned binaries: some antivirus engines have flagged the release, which the project documents as a false positive.
Codebase exploration and understanding
Side-by-Side Comparison
Features
Use Cases
Best For
FAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.