codebase-memory-mcp vs Context Mode
Side-by-side comparison of two AI agent tools
Short answer
- Context Mode is growing faster: +7,280 GitHub stars in the last 30 days vs +1,620 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 Context Mode for: mCP server that sandboxes tool output, persists session memory, and enforces routing across platforms.
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
C
Context Modeopen-source
MCP server that sandboxes tool output, persists session memory, and enforces routing across platforms
Metrics
| codebase-memory-mcp | Context Mode | |
|---|---|---|
| Stars | 45.7k | 25.1k |
| Star velocity /mo | 1.6k | 7.3k |
| Commits (90d) | 2.0k | 141 |
| Releases (6m) | 10 | 10 |
| Downloads (30d, npm + PyPI) | 64.6K | 88.9K |
| Overall score | 0.8944758248474755 | 0.8332926937375552 |
FAQ
- Which is more popular, codebase-memory-mcp or Context Mode?
- codebase-memory-mcp has more GitHub stars (45,713 vs 25,150).
- Which is more actively developed, codebase-memory-mcp or Context Mode?
- codebase-memory-mcp had more commits in the last 90 days (2,034 vs 141).
- Should I use codebase-memory-mcp or Context Mode?
- 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.