codebase-memory-mcp vs Nuclear
Side-by-side comparison of two AI agent tools
Short answer
- codebase-memory-mcp is growing faster: +1,725 GitHub stars in the last 30 days vs +180 for Nuclear.
- Pick codebase-memory-mcp for: mCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP. Pick Nuclear for: streaming music player that finds free music for you.
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
N
Nuclearopen-source
Streaming music player that finds free music for you
Metrics
| codebase-memory-mcp | Nuclear | |
|---|---|---|
| Stars | 45.7k | 18.6k |
| Star velocity /mo | 1.7k | 180 |
| Commits (90d) | 2.1k | 478 |
| Releases (6m) | 10 | 10 |
| Overall score | 0.906371149690189 | 0.7483328722879592 |
FAQ
- Which is more popular, codebase-memory-mcp or Nuclear?
- codebase-memory-mcp has more GitHub stars (45,666 vs 18,572).
- Which is more actively developed, codebase-memory-mcp or Nuclear?
- codebase-memory-mcp had more commits in the last 90 days (2,093 vs 478).
- Should I use codebase-memory-mcp or Nuclear?
- 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.