codebase-memory-mcp vs MCP
Side-by-side comparison of two AI agent tools
Short answer
- codebase-memory-mcp is growing faster: +1,620 GitHub stars in the last 30 days vs +50 for MCP.
- Pick codebase-memory-mcp for: mCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP. Pick MCP for: open source MCP Servers for AWS.
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
M
MCPopen-source
Open source MCP Servers for AWS
Metrics
| codebase-memory-mcp | MCP | |
|---|---|---|
| Stars | 45.7k | 9.7k |
| Star velocity /mo | 1.6k | 50 |
| Commits (90d) | 2.0k | 235 |
| Releases (6m) | 10 | 10 |
| Downloads (30d, npm + PyPI) | 70.9K | — |
| Overall score | 0.8944758248474755 | 0.6555371915325018 |
FAQ
- Which is more popular, codebase-memory-mcp or MCP?
- codebase-memory-mcp has more GitHub stars (45,713 vs 9,749).
- Which is more actively developed, codebase-memory-mcp or MCP?
- codebase-memory-mcp had more commits in the last 90 days (2,034 vs 235).
- Should I use codebase-memory-mcp or MCP?
- 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.