codebase-memory-mcp vs sonic-match-mcp
Side-by-side comparison of two AI agent tools
Short answer
- codebase-memory-mcp is growing faster: +1,548 GitHub stars a month on average vs +0 for sonic-match-mcp.
- Pick codebase-memory-mcp for: mCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP. Pick sonic-match-mcp for: mCP server that watches video footage and returns license-safe BGM matches, hook windows, and ffmpeg ducking.
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
s
sonic-match-mcpopen-source
MCP server that watches video footage and returns license-safe BGM matches, hook windows, and ffmpeg ducking specs for agents.
Metrics
| codebase-memory-mcp | sonic-match-mcp | |
|---|---|---|
| Stars | 45.8k | 153 |
| Star velocity /mo | 1.5k | — |
| Commits (90d) | 2.0k | — |
| Releases (6m) | 10 | — |
| Downloads (30d, npm + PyPI) | 72.1K | — |
| Overall score | 0.8942552721677052 | 0 |
FAQ
- Which is more popular, codebase-memory-mcp or sonic-match-mcp?
- codebase-memory-mcp has more GitHub stars (45,809 vs 153).
- Should I use codebase-memory-mcp or sonic-match-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.