gitnexus: Map Codebases for AI Agents with Knowledge Graphs

Overview

GitNexus is a code intelligence engine built on LadybugDB and Tree-sitter. It indexes source code into a knowledge graph of symbols, dependencies, call chains, and execution flows, giving AI coding agents a structured view of a codebase instead of relying only on text search or generated descriptions.

Its primary workflow is a local CLI connected to editors and agents through MCP. A browser-based UI is also available for visual exploration and chat, with a backend option for repositories too large for browser memory. The project is aimed at developers who want agents to understand code relationships before making or reviewing changes.

Key Features

• Index repositories into a persistent LadybugDB graph using Tree-sitter parsing.
• Provide MCP tools for search, symbol context, impact analysis, call tracing, change detection, and structural checks.
• Connect to coding environments including Claude Code, Cursor, Codex, Antigravity, Windsurf, and OpenCode.
• Generate skills and context files to help supported agents navigate a repository.
• Explore graphs and chat with repositories through a browser UI, or connect that UI to a local server.
• Analyze repository groups to inspect contracts and links across services.
• Offer optional embeddings for semantic search alongside keyword search.

Use Cases

• A developer preparing a refactor can inspect callers and affected execution flows before changing a shared symbol.
• A team using MCP-capable coding agents can give them indexed architectural context while they implement features or debug issues.
• Someone exploring an unfamiliar repository can use the browser UI to inspect code structure without configuring an editor integration.
• Teams working across multiple services can group repositories and examine cross-repository contracts and impact.

Getting Started

From the root of a Git repository, run:

npx gitnexus analyze
npx gitnexus setup

The first command indexes the repository; the second configures detected editor integrations. See the README for setup options, supported integrations, and deployment details.

License in Plain Words

No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.

Alternatives

• GitNexus: This is another GitNexus catalog entry, describing the same codebase knowledge graph and CLI/MCP use case.
• graphify: Graphify builds graphs from code plus docs and schemas, while GitNexus focuses on code indexing with Tree-sitter and LadybugDB.
• codegraph: CodeGraph emphasizes source retrieval and call paths across many languages; GitNexus also offers a browser UI for repository exploration.
• codebase-memory-mcp: codebase-memory-mcp centers on a persistent local graph exposed through MCP, whereas GitNexus also provides a CLI and browser UI.

Considerations

• The project is young but active: recent commit activity is regular, while there has been no release in over a year. Its feature surface may change quickly.
• Contributor activity is not concentrated in one person, based on the supplied health data. The data also reports no recent issue closures or merged pull requests, so do not assume a particular support response cadence.
• Node.js is required for the CLI. The README describes native dependencies and optional language grammars, which can affect installation on machines without a C++ toolchain.
• The browser UI is limited by browser memory for larger repositories; backend mode is provided for scaling beyond that constraint.
• The README identifies the license as PolyForm Noncommercial, while the repository metadata reports no asserted license. Confirm the actual license files and terms before using it commercially.
• The supplied project requirements data does not report a test suite, so teams with strict validation requirements should assess their own workflows before relying on it.