codebase-memory-mcp vs gitnexus
Code knowledge graphs for AI-assisted code exploration
codebase-memory-mcp and gitnexus index repositories into code knowledge graphs that help developers and AI agents explore relationships and assess changes. codebase-memory-mcp focuses on a local MCP server with persistent SQLite storage, while gitnexus offers CLI, MCP, and browser-based exploration, including repository chat in its UI.
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: Map Codebases for AI Agents with Knowledge Graphs
GitNexus builds a codebase knowledge graph with LadybugDB and Tree-sitter, then exposes it through MCP tools for AI coding agents. Use its local CLI for ongoing development or its browser UI for quick repository exploration.
| codebase-memory-mcp | gitnexus | |
|---|---|---|
| Language | C | TypeScript |
| License | MIT | — |
| Stars | 45.7k | 175 |
| Forks | 3.8k | 16 |
| Last analyzed | Oct 3, 2026 | Oct 22, 2026 |
Key differences
- codebase-memory-mcp is written in C; gitnexus is written in TypeScript.
- codebase-memory-mcp stores graph data locally in SQLite and supports automatic change detection and re-indexing; gitnexus offers local CLI indexing and browser-based analysis.
- codebase-memory-mcp provides structural queries, semantic and full-text search, and optional graph visualization; gitnexus adds browser-based AI-assisted repository chat and agent skill generation.
- codebase-memory-mcp is licensed MIT; gitnexus metadata says NOASSERTION, while its README displays a PolyForm Noncommercial license badge.
- codebase-memory-mcp is a structural backend that needs an MCP-compatible client for language-model interaction; gitnexus also offers a browser UI for exploring repositories without first configuring an editor integration.
- codebase-memory-mcp reports 45.7k stars and 3.8k forks; gitnexus reports 173 stars and 16 forks.
Choose codebase-memory-mcp if you…
- need a local MCP backend with persistent SQLite graph storage and automatic re-indexing.
- want semantic and full-text search alongside structural graph queries.
- need to trace HTTP routes and calls across services or index Dockerfiles and Kubernetes resources.
Choose gitnexus if you…
- want CLI, MCP, and browser-based options for repository exploration.
- need browser-based AI-assisted repository chat or generated agent skills and context files.
- work across related repositories and want to group indexes for contract and impact analysis.
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.