Comparison
codebase-memory-mcp vs repobench
Verdict
Pick codebase-memory-mcp if codebase-memory-mcp excels at indexing codebases into a persistent knowledge graph with support for 158 languages, sub-ms query times, and minimal token use, delivered as a single static binary; pick repobench if repoBench assesses repository-level code auto-completion systems, offering benchmarks crucial for researchers and developers working on similar systems.
Markdown twin · codebase-memory-mcp alternatives · repobench alternatives
GraphCanon updated 2w
Trust & integrity
| Signal | codebase-memory-mcp | repobench |
|---|---|---|
| Maintenance | Very active (0d since push) As of 4w · github_public_v1 | Dormant (719d since push) As of 2w · github_public_v1 |
| Provenance | Not a fork · Personal account As of 4w · github_public_v1 | Not a fork · Personal account As of 2w · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of 1mo · osv@v1 | No published findings from this source as of 2026-07-11 As of 1mo · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- codebase-memory-mcp
- High-performance code intelligence MCP server indexing codebases into a persistent knowledge graph quickly
- repobench
- Benchmarking Repository-Level Code Auto-Completion Systems
Stars
- codebase-memory-mcp
- 35k
- repobench
- 214
Forks
- codebase-memory-mcp
- 2.8k
- repobench
- 13
Open issues
- codebase-memory-mcp
- 348
- repobench
- 12
Language
- codebase-memory-mcp
- C
- repobench
- Python
Adopt for
- codebase-memory-mcp
- codebase-memory-mcp excels at indexing codebases into a persistent knowledge graph with support for 158 languages, sub-ms query times, and minimal token use, delivered as a single static binary.
- repobench
- RepoBench assesses repository-level code auto-completion systems, offering benchmarks crucial for researchers and developers working on similar systems.
Persona
- codebase-memory-mcp
- -
- repobench
- -
Runtime
- codebase-memory-mcp
- -
- repobench
- -
License
- codebase-memory-mcp
- MIT
- repobench
- CC-BY-4.0
Last pushed
- codebase-memory-mcp
- Jul 26, 2026
- repobench
- Aug 16, 2024
Categories
- codebase-memory-mcp
- Data & Retrieval, Developer Tools
- repobench
- Developer Tools
Trust and health
Maintenance
- codebase-memory-mcp
- Very active (96%)
- repobench
- Dormant (18%)
Days since push
- codebase-memory-mcp
- 0d
- repobench
- 719d
Open issues (now)
- codebase-memory-mcp
- 348
- repobench
- 12
OSV dependency advisories
- codebase-memory-mcp
- No lockfile (source not queried)
- repobench
- No published findings from this source as of 2026-07-11
Full report
- codebase-memory-mcp
- Trust report
- repobench
- Trust report
Choose codebase-memory-mcp if…
- codebase-memory-mcp is primarily C; repobench is Python.
- License: codebase-memory-mcp is MIT, repobench is CC-BY-4.0.
- Tags unique to codebase-memory-mcp: aider, ast, claude-code, code-analysis.
- Also covers Data & Retrieval.
- When needing rapid codebase indexing into a knowledge graph with low latency queries
When NOT to use codebase-memory-mcp
- If you demand extensive interactive graphical UI features beyond its command-line interface capabilities
- When your project prioritizes a dynamic runtime environment over static binaries
Choose repobench if…
- repobench is primarily Python; codebase-memory-mcp is C.
- License: repobench is CC-BY-4.0, codebase-memory-mcp is MIT.
- Tags unique to repobench: benchmarking, code-completion, iclr 2024.
- Use RepoBench if you are evaluating the performance of your own repository-level code completion system against established benchmarks.
When NOT to use repobench
- Do not use RepoBench if your focus is on line-level or function-level code completions as opposed to repository-wide assessments.
- Avoid RepoBench in scenarios where you require real-time analytics rather than benchmarking against static datasets and predefined criteria.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (DeusData/codebase-memory-mcp) · observed Jul 26, 2026
- GitHub forks (DeusData/codebase-memory-mcp) · observed Jul 26, 2026
- Last push (DeusData/codebase-memory-mcp) · observed Jul 26, 2026
- License file (MIT) · observed Jul 26, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (Leolty/repobench) · observed Aug 5, 2026
- GitHub forks (Leolty/repobench) · observed Aug 5, 2026
- Last push (Leolty/repobench) · observed Aug 16, 2024
- License file (CC-BY-4.0) · observed Aug 5, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: codebase-memory-mcp 35k · repobench 214 (synced Jul 26, 2026).
Common questions
- What is the difference between codebase-memory-mcp and repobench?
- codebase-memory-mcp: High-performance code intelligence MCP server indexing codebases into a persistent knowledge graph quickly. repobench: Benchmarking Repository-Level Code Auto-Completion Systems. See the comparison table for live GitHub stats and shared categories.
- When should I choose codebase-memory-mcp over repobench?
- Choose codebase-memory-mcp over repobench when codebase-memory-mcp is primarily C; repobench is Python; License: codebase-memory-mcp is MIT, repobench is CC-BY-4.0; Tags unique to codebase-memory-mcp: aider, ast, claude-code, code-analysis; Also covers Data & Retrieval; When needing rapid codebase indexing into a knowledge graph with low latency queries.
- When should I choose repobench over codebase-memory-mcp?
- Choose repobench over codebase-memory-mcp when repobench is primarily Python; codebase-memory-mcp is C; License: repobench is CC-BY-4.0, codebase-memory-mcp is MIT; Tags unique to repobench: benchmarking, code-completion, iclr 2024; Use RepoBench if you are evaluating the performance of your own repository-level code completion system against established benchmarks.
- When should I avoid codebase-memory-mcp?
- If you demand extensive interactive graphical UI features beyond its command-line interface capabilities When your project prioritizes a dynamic runtime environment over static binaries
- When should I avoid repobench?
- Do not use RepoBench if your focus is on line-level or function-level code completions as opposed to repository-wide assessments. Avoid RepoBench in scenarios where you require real-time analytics rather than benchmarking against static datasets and predefined criteria.
- Is codebase-memory-mcp or repobench more popular on GitHub?
- codebase-memory-mcp has more GitHub stars (35,386 vs 214). Stars measure visibility, not whether either tool fits your constraints.
- Are codebase-memory-mcp and repobench open source?
- Yes - both are open-source projects on GitHub (codebase-memory-mcp: MIT, repobench: CC-BY-4.0).
- Where can I find alternatives to codebase-memory-mcp or repobench?
- GraphCanon lists graph-backed alternatives at codebase-memory-mcp alternatives and repobench alternatives (codebase-memory-mcp markdown twin, repobench markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, codebase-memory-mcp or repobench?
- codebase-memory-mcp: Very active. repobench: Dormant. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for codebase-memory-mcp and repobench?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: codebase-memory-mcp trust report; repobench trust report.