codebase-memory-mcp vs Hypit
Side-by-side comparison of two AI agent tools
Short answer
- Hypit is growing faster: +12,420 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 Hypit for: a language and system for AI agents to clone or create videos with footage, captions, B-roll, and effects.
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
H
Hypitfree
A language and system for AI agents to clone or create videos with footage, captions, B-roll, and effects
Metrics
| codebase-memory-mcp | Hypit | |
|---|---|---|
| Stars | 45.6k | 18.4k |
| Star velocity /mo | 1.5k | 12.4k |
| Commits (90d) | 2.1k | 1.4k |
| Releases (6m) | 10 | 10 |
| Overall score | 0.9054235547012244 | 0.9292096852015334 |
FAQ
- Which is more popular, codebase-memory-mcp or Hypit?
- codebase-memory-mcp has more GitHub stars (45,600 vs 18,394).
- Which is more actively developed, codebase-memory-mcp or Hypit?
- codebase-memory-mcp had more commits in the last 90 days (2,148 vs 1,418).
- Should I use codebase-memory-mcp or Hypit?
- Compare their capabilities, limitations and "best for" notes above. Trying each on a small task is the fastest way to decide.