GitNexus
Knowledge graph for any codebase — runs in browser via WASM
Expert verdict
Ship
3-1The Panel's Take
GitNexus is a zero-server code intelligence engine that solves one of the core limitations of LLM coding assistants: they rediscover code structure from scratch on every query. Instead, GitNexus precomputes a full knowledge graph of your codebase — every function, dependency, call chain, and execution flow — then exposes it through a Graph RAG agent and native MCP tools for editors like Claude Code, Cursor, and Codex CLI. The architecture is unusual: the entire engine compiles to WebAssembly, meaning it runs both in Node.js and fully client-side in the browser without any server infrastructure. The Graph RAG layer performs multi-hop reasoning over the code graph rather than simple embedding similarity, which means it can answer "what would break if I change this function" rather than just "where is this function defined." MCP tool exposure means AI agents in supporting editors can query the graph natively. The tool gained 837 new GitHub stars today as it caught a second wave of attention after its February launch. It's particularly compelling for monorepos and multi-language projects where file-by-file context injection fails. The PolyForm Noncommercial license makes it free for open-source projects, with commercial licensing available through AkonLabs for teams.
Share this verdict
GitNexus verdict: SHIP 🚀 3 ships · 1 skip from the expert panel Full review: shiporskip.io/tool/gitnexus-knowledge-graph-codebase-graph-rag-mcp-wasm
Weekly AI Tool Verdicts
Get the next verdict in your inbox
7 critics review a new AI tool every day. Weekly digest — free.
Similar Products
Compare GitNexus with Others
Looking for GitNexus alternatives?
Compare GitNexus with every other Developer Tools tool reviewed by our panel.
See all Developer Tools alternativesEmbed this verdict
Tool makers can add a live ShipOrSkip badge to their site. Badge loads track impressions; clicks route back to this review.
<a href="https://shiporskip.io/api/badge-click/gitnexus-knowledge-graph-codebase-graph-rag-mcp-wasm" target="_blank" rel="noopener"><img src="https://shiporskip.io/api/badge/gitnexus-knowledge-graph-codebase-graph-rag-mcp-wasm" alt="GitNexus Ship verdict on ShipOrSkip" width="360" height="90" /></a>[](https://shiporskip.io/api/badge-click/gitnexus-knowledge-graph-codebase-graph-rag-mcp-wasm)<iframe src="https://shiporskip.io/embed/gitnexus-knowledge-graph-codebase-graph-rag-mcp-wasm" title="GitNexus ShipOrSkip verdict" width="360" height="260" style="border:0;border-radius:16px;max-width:100%;" loading="lazy"></iframe>The reviews
“This tackles something I've been hacking around manually — pre-feeding dependency graphs into context windows before big refactors. The Graph RAG approach is genuinely smarter than pure embedding similarity for code questions. The MCP integration means it slots directly into Claude Code without any glue code.”
“Knowledge graphs for code have been tried many times — they age quickly as the codebase evolves and require constant re-indexing to stay accurate. The PolyForm Noncommercial license is ambiguous enough to cause legal anxiety for any commercial team. Wait for a clear SaaS tier with managed indexing before committing.”
“The WASM-first architecture is prescient — it means GitNexus can live inside browser-based dev environments like StackBlitz and CodeSandbox without any server costs. As AI coding agents become first-class citizens of IDEs, pre-computed code graphs become the memory layer those agents rely on. This is early infrastructure.”
“I don't write code professionally but I use AI tools to build side projects, and the 'why is this breaking everything' question is my biggest frustration. A tool that maps what depends on what and can answer those questions in plain language would genuinely change how I work with AI assistants.”