The 17 MCP tools answer structural questions beyond text search
GitNexus exposes 17 tools for symbol context, path tracing, upstream impact, pending diffs, route maps, and raw Cypher. It indexes files, symbols, imports, calls, inheritance, clusters, and detected execution paths into LadybugDB. Claude Code, Codex, Cursor, and other clients receive a prepared structural view of a repository instead of another pile of matching text.
The parser table covers 14 languages, including TypeScript, Python, Java, Go, Rust, PHP, C#, and C++. Coverage differs by language, which the README shows column by column. The browser explorer runs with WebAssembly and keeps code in the browser, but the documented memory ceiling is roughly 5,000 files. Larger projects belong on the native CLI or local backend.
Two setup commands also write agent and editor configuration
GitNexus analysis may write 2 agent files, AGENTS.md and CLAUDE.md, before editor setup changes MCP configuration. The advertised path is to run npx gitnexus analyze in a repository, then run npx gitnexus setup once. Analysis creates the graph, registers its path globally, and installs agent skills. Claude Code and Codex can also receive hooks that add graph context around tool calls and warn after commits make the index stale.
Those changes are useful, but teams with controlled worktrees should inspect them before accepting defaults. Skip flags can preserve context files or avoid skills. MCP has a read-only mode, repository allowlists, a default-repository setting, and response budgets for 3 common query tools. The controls are detailed enough for a shared developer machine, provided someone takes responsibility for the policy rather than running every tool with its default access.
What happened when we ran it
Our measurement setup installed commit aac7515 in 15 seconds inside an unprivileged Node 22 Debian container with 3 CPUs and 8 GB RAM. npm added 205 packages, and the resulting dependency tree occupied 93 MB on disk. The checkout contained 4,872 files and about 727,589 lines of source in 32.6 MB. npm audit reported 0 known vulnerabilities across critical, high, moderate, and low severity.
The root package exposed no build target, so we skipped the build rather than inventing one. It also exposed no test target, and there was no tests directory, so no test suite ran. The repository did contain 29 CI workflow files. That is evidence of extensive automation in the project, but it does not replace a reproducible root build or test command for a fresh contributor.
Fourteen parsers do not provide fourteen equal analysis paths
In v1.6.9, control-flow graphs and the program-dependence and taint layer are opt-in and cover TypeScript and JavaScript. Several other languages lack one or more forms of import, binding, heritage, type, or configuration analysis. A polyglot graph can still be useful, but a result from C or Ruby does not carry the same evidence as one from TypeScript.
Recent issues show why the distinction matters. Issue #3040 describes a Convex function with 4 production call sites and 5 test call sites returning zero upstream impact while being labelled exact. Issue #3041 reports same-named nested handlers collapsing into 1 node, which attached calls to the wrong function. Issue #3039 found 18 tracked TypeScript files omitted because directories named env or generated were skipped. These are specific code shapes and do not prove every graph is wrong. They are enough to rule out blind trust.
PolyForm Noncommercial makes this a poor default for companies
GitHub cannot identify the repository license with a standard SPDX value, while the README and LICENSE name PolyForm Noncommercial 1.0.0. The project publishes source, but ordinary commercial use needs separate permission. Akon Labs offers commercial licensing and enterprise deployments. A company evaluating GitNexus should resolve that contract before indexing private work or wiring the tool into every developer's editor.
Network deployment also needs care. Local CLI use keeps the index in .gitnexus/, and the global registry stores paths and metadata. The documented Render blueprint uses 2 services, a private backend, a public web proxy, and an access token stored in session storage. The README says that token is the only control on the deploy and that anyone holding it can read every indexed repository.
A push on August 25 and 337 open items show active, unfinished work
GitNexus had 45,756 stars when we checked, and the last push was August 25, 2026. The latest stable release was v1.6.9 on July 4. GitHub reported 280 open issues and 57 open pull requests, with correctness reports and fixes both updated on August 25. That combination indicates heavy current development rather than a project coasting on an old release. It also means users should pin a version and read changes before rebuilding an important index.
Codebase Memory MCP and Code Review Graph both use MIT licenses and concentrate on local graph context for agents. DeepWiki Open is a better match when the deliverable is a browsable repository explanation rather than callable impact analysis. GitNexus covers more territory with indexing, MCP, editor skills, hooks, a browser graph, multi-repository groups, and optional wiki generation.
Use the graph as a second opinion, not a deletion permit
A 15-second installation and 17 MCP tools make GitNexus easy to trial on one repository. Start in a clean worktree, inspect the files and editor settings it writes, then compare several impact results with text search and language-server references. If it consistently finds cross-module relationships your current agent misses, the local index earns its upkeep. If commercial licensing, automatic configuration changes, or incomplete analysis of a dynamic framework is unacceptable, stop before making it part of the team's default toolchain.