--- title: "codebase-memory-mcp vs dolt" type: "comparison" canonical_url: "https://www.graphcanon.com/compare/deusdata-codebase-memory-mcp-vs-dolthub-dolt" tools: ["deusdata-codebase-memory-mcp", "dolthub-dolt"] --- # codebase-memory-mcp vs dolt *GraphCanon updated Aug 19, 2026* ## Verdict Pick codebase-memory-mcp if codebase-memory-mcp excels at indexing codebases into a persistent knowledge graph with support for 158 languages, sub-ms query times, and minimal token use, delivered as a single static binary; pick dolt if `dolt` merges version control principles from Git with SQL database capabilities to manage data versions effectively. [codebase-memory-mcp](https://deusdata.github.io/codebase-memory-mcp/) reports 35k GitHub stars, 2.8k forks, and 348 open issues, last pushed Jul 26, 2026. [dolt](https://www.dolthub.com) has 24k stars, 860 forks, and 711 open issues, last pushed Aug 19, 2026. Figures are from public GitHub metadata via [codebase-memory-mcp's repository](https://github.com/DeusData/codebase-memory-mcp) and [dolt's repository](https://github.com/dolthub/dolt). | | [codebase-memory-mcp](/tools/deusdata-codebase-memory-mcp.md) | [dolt](/tools/dolthub-dolt.md) | | --- | --- | --- | | Tagline | High-performance code intelligence MCP server indexing codebases into a persistent knowledge graph quickly | Git for Data | | Stars | 35,386 | 24,225 | | Forks | 2,756 | 860 | | Open issues | 348 | 711 | | Language | C | Go | | Adopt for | codebase-memory-mcp excels at indexing codebases into a persistent knowledge graph with support for 158 languages, sub-ms query times, and minimal token use, delivered as a single static binary. | `dolt` merges version control principles from Git with SQL database capabilities to manage data versions effectively. | | Persona | - | - | | Runtime | - | - | | License | MIT | Apache-2.0 | | Categories | Data & Retrieval, Developer Tools | Data & Retrieval | ## Trust and health _Sourced signals - not a safety guarantee. No winner column._ | | [codebase-memory-mcp](/tools/deusdata-codebase-memory-mcp.md) | [dolt](/tools/dolthub-dolt.md) | | --- | --- | --- | | Open issues (now) | 348 | 711 | | Stars delta | Unknown | +318 (30d) | | Open issues delta | Unknown | +119 (30d) | | Owner type | User | Organization | | Full report | [trust report](/tools/deusdata-codebase-memory-mcp/trust.md) | [trust report](/tools/dolthub-dolt/trust.md) | ## Decision facts: codebase-memory-mcp - **Adopt for:** codebase-memory-mcp excels at indexing codebases into a persistent knowledge graph with support for 158 languages, sub-ms query times, and minimal token use, delivered as a single static binary. ## Decision facts: dolt - **Adopt for:** `dolt` merges version control principles from Git with SQL database capabilities to manage data versions effectively. ## Choose when ### Choose codebase-memory-mcp if… - codebase-memory-mcp is primarily C; dolt is Go. - License: codebase-memory-mcp is MIT, dolt is Apache-2.0. - Tags unique to codebase-memory-mcp: aider, ast, claude-code, code-analysis. - Also covers Developer Tools. - When needing rapid codebase indexing into a knowledge graph with low latency queries ### Choose dolt if… - dolt is primarily Go; codebase-memory-mcp is C. - License: dolt is Apache-2.0, codebase-memory-mcp is MIT. - Tags unique to dolt: agent-memory, ai-database, data-version-control, database-versioning. - Use `dolt` when you need a system that treats your data like source code, allowing for branching, merging, and rollback operations similar to software development practices. ## When NOT to use codebase-memory-mcp - If you demand extensive interactive graphical UI features beyond its command-line interface capabilities - When your project prioritizes a dynamic runtime environment over static binaries ## When NOT to use dolt - If a simple, monolithic relational database with no need for historical data versioning is sufficient, then `dolt` might introduce unnecessary complexity. - Avoid using `dolt` if your primary requirement is real-time transaction processing without the overhead of maintaining multiple versions of your dataset. ## Common questions ### What is the difference between codebase-memory-mcp and dolt? codebase-memory-mcp: High-performance code intelligence MCP server indexing codebases into a persistent knowledge graph quickly. dolt: Git for Data. See the comparison table for live GitHub stats and shared categories. ### When should I choose codebase-memory-mcp over dolt? Choose codebase-memory-mcp over dolt when codebase-memory-mcp is primarily C; dolt is Go; License: codebase-memory-mcp is MIT, dolt is Apache-2.0; Tags unique to codebase-memory-mcp: aider, ast, claude-code, code-analysis; Also covers Developer Tools; When needing rapid codebase indexing into a knowledge graph with low latency queries. ### When should I choose dolt over codebase-memory-mcp? Choose dolt over codebase-memory-mcp when dolt is primarily Go; codebase-memory-mcp is C; License: dolt is Apache-2.0, codebase-memory-mcp is MIT; Tags unique to dolt: agent-memory, ai-database, data-version-control, database-versioning; Use `dolt` when you need a system that treats your data like source code, allowing for branching, merging, and rollback operations similar to software development practices. ### When should I avoid codebase-memory-mcp? If you demand extensive interactive graphical UI features beyond its command-line interface capabilities When your project prioritizes a dynamic runtime environment over static binaries ### When should I avoid dolt? If a simple, monolithic relational database with no need for historical data versioning is sufficient, then `dolt` might introduce unnecessary complexity. Avoid using `dolt` if your primary requirement is real-time transaction processing without the overhead of maintaining multiple versions of your dataset. ### Is codebase-memory-mcp or dolt more popular on GitHub? codebase-memory-mcp has more GitHub stars (35,386 vs 24,225). Stars measure visibility, not whether either tool fits your constraints. ### Are codebase-memory-mcp and dolt open source? Yes - both are open-source projects on GitHub (codebase-memory-mcp: MIT, dolt: Apache-2.0). ### Where can I find alternatives to codebase-memory-mcp or dolt? GraphCanon lists graph-backed alternatives at [codebase-memory-mcp alternatives](/tools/deusdata-codebase-memory-mcp/alternatives) and [dolt alternatives](/tools/dolthub-dolt/alternatives) ([codebase-memory-mcp markdown twin](/tools/deusdata-codebase-memory-mcp/alternatives.md), [dolt markdown twin](/tools/dolthub-dolt/alternatives.md)), ranked by typed relationship edges rather than popularity votes. ### Is there a machine-readable version of this comparison? Yes. The markdown twin at [this comparison](/compare/deusdata-codebase-memory-mcp-vs-dolthub-dolt.md) mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers. ### Which is better maintained, codebase-memory-mcp or dolt? codebase-memory-mcp: Very active. dolt: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance. ### Where are the full trust reports for codebase-memory-mcp and dolt? GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: [codebase-memory-mcp trust report](/tools/deusdata-codebase-memory-mcp/trust); [dolt trust report](/tools/dolthub-dolt/trust). --- **Machine-readable endpoints** - JSON: [`/api/graphcanon/graph?tool=deusdata-codebase-memory-mcp`](/api/graphcanon/graph?tool=deusdata-codebase-memory-mcp) - LLM index: [/llms.txt](/llms.txt) - Full corpus: [/llms-full.txt](/llms-full.txt) _GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_