Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
codebase-memory-mcp earned a place on the map:
How we mapped it:
- alternative to
tokensave — The same exact job — pre-indexed structural code intelligence over MCP so agents stop grepping. TokenSave is a libSQL semantic graph across 50+ languages; codebase-memory is a zero-dependency C binary betting everything on speed: 158 languages, sub-ms.
- alternative to
code-review-graph — Both build tree-sitter AST graphs served over MCP with blast-radius answers. code-review-graph is tuned for the review workflow (82x fewer tokens per review question); codebase-memory is the general-purpose engine with LSP-grade types.
- alternative to
cocoindex-code — The two query styles of agent code context: cocoindex-code embeds AST chunks for semantic 'find the code that does X'; codebase-memory graphs symbols for structural 'who calls this and what breaks'. Different questions — many stacks want both.
If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.
Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
codebase-memory-mcp earned a place on the map:
How we mapped it:
tokensave— The same exact job — pre-indexed structural code intelligence over MCP so agents stop grepping. TokenSave is a libSQL semantic graph across 50+ languages; codebase-memory is a zero-dependency C binary betting everything on speed: 158 languages, sub-ms.code-review-graph— Both build tree-sitter AST graphs served over MCP with blast-radius answers. code-review-graph is tuned for the review workflow (82x fewer tokens per review question); codebase-memory is the general-purpose engine with LSP-grade types.cocoindex-code— The two query styles of agent code context: cocoindex-code embeds AST chunks for semantic 'find the code that does X'; codebase-memory graphs symbols for structural 'who calls this and what breaks'. Different questions — many stacks want both.If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.