What it is
GitNexus indexes a repository into a knowledge graph of symbols, calls, dependencies, functional clusters and execution flows, then serves it to coding agents through 19 MCP tools. Because the structure is precomputed, tools such as impact (the blast radius of a change), context (a full view of one symbol), detect_changes (map a git diff to affected flows), trace and rename answer in one call. There is also a raw Cypher query tool, statement-level data-flow queries for indexes built with --pdg, and a browser Web UI for exploring the graph.
npx gitnexus analyze builds the index and, by default, installs agent skills, registers Claude Code hooks and writes AGENTS.md and CLAUDE.md; --index-only skips those files. npx gitnexus setup writes MCP config for eight editors. The README lists 18 languages with registered providers, from C and COBOL to TypeScript, Vue and Zig. Indexing runs locally without an LLM.
The repo has about 48,000 stars and ships release candidates several times a day (1.6.13-rc.148 on 23 October 2026), while the npm latest tag stays on 1.6.12. It is licensed under PolyForm Noncommercial 1.0.0, not an open-source licence; commercial use goes through Akon Labs.
Install
npx gitnexus analyze && npx gitnexus setupOur review
GitNexus gives an agent more structural understanding of a codebase than any other server in this category, and its licence keeps it out of most offices. Both facts matter equally to anyone evaluating it.
The tool surface goes well past semantic search. impact groups affected symbols by depth with a confidence score, detect_changes maps changed lines to execution flows, rename previews by default and applies only the reviewed edits via a plan_token, and route_map, shape_check and api_impact trace API handlers to the components that call them. For indexes built with --pdg there are statement-level control and data-dependence queries and taint findings. code-review-graph covers some of the same ground under MIT, with less depth.
The licence is PolyForm Noncommercial. Personal projects, study and non-profit work are fine; a company using it, even for a pilot, needs a commercial licence, which the README says is available "with proper licensing" and prices nowhere. PR review, auto-reindexing, a unified multi-repo graph and OCaml support are reserved for the enterprise offering.
The defaults lean permissive. analyze writes hooks, skills and context files into your repository unless you pass --index-only, and raw Cypher plus write-capable rename are exposed unless GITNEXUS_MCP_READ_ONLY=1 is set. The documented Render deployment, about $35 a month, rests on a single access token; the docs point out that the proxy strips Origin, so the CSRF guard does nothing and anyone with the token can read every indexed repository.
The release cadence cuts both ways. 148 release candidates have landed on 1.6.13 while npm's latest tag sits on 1.6.12, so npx users get the stable build and anyone tracking rc gets fixes within hours, and behaviour changes with them.
Where it earns its place
A maintainer of a large open-source TypeScript monorepo
See what a contributor's pull request really touches before merging
Check out the branch, run gitnexus analyze --index-only, then have the agent run detect_changes and impact on the diff to list affected flows by depth. Noncommercial open-source use is within the licence and indexing is local, so it costs nothing.
A PhD student studying a legacy COBOL and Java system
Map how a batch job flows through code nobody documented
Index once, browse clusters and processes in the Web UI through gitnexus serve, and use trace to follow the call path between two symbols. Academic research is covered by PolyForm Noncommercial.
An engineering manager at a 50-developer fintech
Decide whether to roll it out to the team
Even a pilot is commercial use, so it starts with a licence enquiry to Akon Labs. For the trial, set GITNEXUS_MCP_READ_ONLY=1 and GITNEXUS_MCP_ALLOWED_REPOS so agents cannot run raw Cypher or apply renames, and expect PR review to need the enterprise tier.
Before you commit
- Setup
- Node.js 22.18+ or 24.11+, then npx gitnexus analyze in the repository root and npx gitnexus setup, which detects Claude Code, Cursor, Codex, Antigravity, Factory Droid, OpenCode, CodeBuddy and Qoder; Windsurf needs manual config. The README advises npm install -g gitnexus for repeated use.
- Integrations
- 19 MCP tools (17 per repository, 2 for repository groups), 10 resources and 2 prompts. Most are read tools such as query, context, impact, trace, detect_changes and grep; rename can apply edits and cypher runs arbitrary graph queries. One shared HTTP server on port 3111 serves several agents.
- Data and privacy
- Indexing is local and uses no LLM; remote embeddings, wiki generation and the Web UI's AI chat send code to providers you configure. read_file and grep read the working tree. On the Render deployment a single token guards every indexed repository.
- Cost at scale
- Free for noncommercial use; commercial and enterprise licences are priced on enquiry. The documented Render deployment costs about $35 a month: $25 for the server, $7 for the web service and $2.50 for a 10 GB disk.
- Limits
- Resolution varies by language construct, and the README tells users to check reported ambiguity and index freshness. Without --watch the index goes stale; auto-reindexing is enterprise-only. Large responses can be capped with maxTokens or GITNEXUS_MCP_DEFAULT_MAX_TOKENS.
What's good
- 19 tools including impact, detect_changes, trace and previewed rename
- Indexes locally with no LLM; embeddings optional
- 18 languages with registered providers
- Read-only mode, repository allowlist and response token caps
What's not
- PolyForm Noncommercial; commercial licence prices unpublished
- analyze writes hooks, skills and context files unless --index-only
- Raw Cypher and applied renames on by default
- PR review, auto-reindexing and unified multi-repo graph held for enterprise
Best for
Individual developers, researchers and open-source maintainers on noncommercial projects who want the deepest structural view of a codebase for their agent.
Alternatives
GitNexus: common questions
- Is GitNexus worth it?
- Exceptional code intelligence for agents, held back by a noncommercial licence that most employers cannot accept without a paid deal. We rate it 3.9 out of 5.
- How much does GitNexus cost?
- Free for noncommercial use (PolyForm Noncommercial 1.0.0). Commercial use, managed SaaS and self-hosted enterprise deployments need a licence from Akon Labs; prices are not published.
- What are the downsides of GitNexus?
- PolyForm Noncommercial; commercial licence prices unpublished; analyze writes hooks, skills and context files unless --index-only; raw Cypher and applied renames on by default; pR review, auto-reindexing and unified multi-repo graph held for enterprise.
- Who is GitNexus best for?
- Individual developers, researchers and open-source maintainers on noncommercial projects who want the deepest structural view of a codebase for their agent.
- How much does GitNexus cost for a team or in production?
- Free for noncommercial use; commercial and enterprise licences are priced on enquiry. The documented Render deployment costs about $35 a month: $25 for the server, $7 for the web service and $2.50 for a 10 GB disk.
- Is GitNexus safe for company data?
- Indexing is local and uses no LLM; remote embeddings, wiki generation and the Web UI's AI chat send code to providers you configure. read_file and grep read the working tree. On the Render deployment a single token guards every indexed repository.
- What are the best GitNexus alternatives?
- The closest alternatives we have reviewed are code-review-graph, Serena, Semble and GitHub MCP Server.
Answers checked Oct 23, 2026.