codebase-memory-mcp vs graphicle
Code intelligence MCP in pure C: tree-sitter knowledge graph over 158 languages, average repo indexed in milliseconds, sub-ms queries, 10x fewer tokens. Single static binary, zero deps. — versus — One Rust program giving coding agents a code graph plus memory of docs, decisions and past sessions, served over MCP to Claude Code, Codex, Cursor and VS Code.
Both serve a tree-sitter code knowledge graph to agents over MCP. codebase-memory-mcp is pure C and code only; Graphicle adds docs, decisions and session memory.
| codebase-memory-mcp | graphicle | |
|---|---|---|
| Stars | 48k | 509 |
| Forks | 4.0k | 36 |
| Language | C | Rust |
| License | MIT | Apache-2.0 |
| Last activity | 2 days ago | yesterday |
| Topics | code-intel, local | code-intel, memory |
| Curated connections | 11 | 5 |
codebase-memory-mcp — the curator's take
The performance ceiling of the code-context-server category: pure C, single static binary, the Linux kernel indexed in 3 minutes, structural queries under a millisecond — with a peer-reviewed preprint (83% answer quality, 10x fewer tokens across 31 repos) instead of vibes. Hybrid LSP adds real type resolution for the 12 languages that matter most, and 43 client surfaces means it plugs into whatever agent you run. NOT semantic search — it answers structural questions (call chains, routes, blast radius), not 'where's the code that does X'; pair it with an embedding tool for that. And note its own disclosure: it writes to your agent config files by design — audit posture is unusually good (SLSA 3, OpenSSF, per-release VirusTotal), use it.
graphicle — the curator's take
Use it when you want code intelligence and project memory from one local install instead of a code-graph MCP plus a separate memory server. Skip it if you already run a dedicated code graph you like, or need team-shared memory. Its memory comparison against seven systems is pre-release and self-reported.