codebase-memory-mcp vs DBX
Side-by-side comparison of two AI agent tools
Short answer
- DBX is growing faster: +16,380 GitHub stars in the last 30 days vs +1,470 for codebase-memory-mcp.
- Pick codebase-memory-mcp for: mCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP. Pick DBX for: 25 MB cross-platform client for 100+ databases with a built-in AI assistant and MCP Server.
From GitHub data refreshed daily.
c
codebase-memory-mcpopen-source
MCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP
D
DBXopen-source
25 MB cross-platform client for 100+ databases with a built-in AI assistant and MCP Server
Metrics
| codebase-memory-mcp | DBX | |
|---|---|---|
| Stars | 45.6k | 23.6k |
| Star velocity /mo | 1.5k | 16.4k |
| Commits (90d) | 2.1k | 4.8k |
| Releases (6m) | 10 | 10 |
| Overall score | 0.9054235547012244 | 0.9550954131257804 |
FAQ
- Which is more popular, codebase-memory-mcp or DBX?
- codebase-memory-mcp has more GitHub stars (45,600 vs 23,621).
- Which is more actively developed, codebase-memory-mcp or DBX?
- DBX had more commits in the last 90 days (4,766 vs 2,148).
- Should I use codebase-memory-mcp or DBX?
- Compare their capabilities, limitations and "best for" notes above. Both are open source, so trying each on a small task is the fastest way to decide.