mexA living wiki for your codebase, written by your coding agents: a Tree-sitter graph grounds structured Markdown notes, task-aware routing loads only what's needed, and drift checks catch stale claims.
Why switchBoth build a Markdown context layer over a large codebase with no embeddings, served through agent hooks and MCP. Graft keeps it to a graph of prose nodes agents read like files; mex puts a Tree-sitter symbol graph underneath so claims can be grounded and drift detected.
Full comparison → ontology-atlasDesktop app plus MCP server keeping a codebase's ontology as reviewable Markdown in the repo: domains and capabilities linked to code evidence, compiled to a graph for blast-radius queries.
Why switchBoth hand agents a hand-written Markdown context layer over a large codebase instead of embeddings. Graft is a flat plain-English node graph with Claude Code hooks; Atlas constrains you to five node kinds and a fixed relation set so the folder becomes computable.
Full comparison → codebase-memory-mcpCode 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.
Why switchSame job — spare agents the re-exploration tax — opposite representations: codebase-memory-mcp serves a symbol-level tree-sitter graph over MCP with sub-ms queries; Graft writes plain-English concept nodes as markdown the agent simply reads.
Full comparison → tokensaveCode-intelligence MCP server for coding agents — a pre-indexed semantic graph (libSQL + FTS5) they query instead of grepping: symbols, callers, impact radius in one call. 100% local, 50+ languages.
Why switchBoth replace blind grepping with a pre-built codebase understanding: tokensave is a queryable semantic index (libSQL + FTS5) behind MCP tools; Graft is prose-first — explanation files injected via hooks, no query API to learn.
Full comparison → code-graph-ragParses a polyglot monorepo with Tree-sitter into a Memgraph knowledge graph: query it in plain English (NL→Cypher), trace data flow, find dead code, edit via AST-surgical patches.
Why switchBoth are context layers for large codebases, opposite philosophies: graft stores plain-English markdown graph nodes agents read as files (no DB, no embeddings); code-graph-rag stores the actual AST-derived graph in Memgraph. Legibility and zero infra vs queryable structure.
Full comparison →