GitNexus vs codebase-memory-mcp
Code knowledge graphs for AI-assisted repository analysis
GitNexus and codebase-memory-mcp index repositories into knowledge graphs and expose code relationships through MCP tools. GitNexus also offers a CLI and browser UI, while codebase-memory-mcp focuses on a local MCP server with persistent SQLite storage and additional search and indexing options.
GitNexus: Map Codebases for AI-Assisted Analysis
GitNexus indexes a codebase as a knowledge graph and exposes its relationships through CLI and MCP tools. It helps developers and AI coding agents trace dependencies, understand execution flows, and assess change impact.
codebase-memory-mcp: Build a Searchable Code Knowledge Graph
A local MCP server that indexes repositories into a persistent graph of code structure and relationships. It helps AI coding agents answer architectural and code-navigation questions with focused queries instead of repeated file searches.
| GitNexus | codebase-memory-mcp | |
|---|---|---|
| Language | TypeScript | C |
| License | NOASSERTION | MIT |
| Stars | 47.7k | 45.7k |
| Forks | 5.2k | 3.8k |
| Last analyzed | Oct 3, 2026 | Oct 3, 2026 |
Key differences
- GitNexus is written in TypeScript; codebase-memory-mcp is written in C.
- GitNexus reports its license as NOASSERTION, while its README displays PolyForm Noncommercial; codebase-memory-mcp is licensed under MIT.
- GitNexus offers local CLI indexing and a browser UI, with browser-only indexing constrained by available memory; codebase-memory-mcp runs locally, stores graph data in SQLite, and supports automatic change detection and re-indexing.
- GitNexus highlights functional clusters and execution flows; codebase-memory-mcp indexes definitions, calls, imports, routes, and types, with Hybrid LSP semantic type resolution for supported languages.
- GitNexus supports repository groups for cross-repository contract discovery and impact analysis; codebase-memory-mcp can link routes and calls across services and index Dockerfiles and Kubernetes resources.
- GitNexus reports 47.7k stars and 5.2k forks; codebase-memory-mcp reports 45.7k stars and 3.8k forks.
Choose GitNexus if you…
- want a CLI and browser UI for indexing, querying, and visually exploring repositories.
- need graph-backed execution-flow and change-impact analysis, including repository groups for cross-repository work.
- are considering selected editor integrations with MCP, skills, or hooks and will review their support and license terms.
Choose codebase-memory-mcp if you…
- want a local MCP server with persistent SQLite graph storage and automatic change detection.
- need semantic and full-text search alongside structural queries, or Hybrid LSP type resolution for supported languages.
- want to explore routes and calls across services or index Dockerfiles and Kubernetes resources.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.