GitNexus
Indexes a codebase into a knowledge graph and gives the agent call chains, change blast radius and code search over MCP
Install
npx gitnexus analyze
npx gitnexus setupRun from the repository root. For faster MCP startup install globally with npm install -g gitnexus first.
This is third-party code. Review the repository files before installing.
What it does
GitNexus parses a repository with Tree-sitter and builds a local graph of dependencies, call chains, clusters and execution flows. Over MCP the agent gets tools for hybrid search, a full symbol view with references, change impact analysis, path tracing between functions, git diff impact and coordinated multi-file rename. The analyze command also installs a skill set (exploring, debugging, refactoring, review, impact analysis), Claude Code hooks and AGENTS.md and CLAUDE.md files. A browser-only web UI is also available.
Who it is for. For developers on large codebases whose agent breaks dependencies because it cannot see the whole project structure.
Good fit when
- You need to know what depends on a function before editing it
- You need to see which flows the current diff touches
- You need to rename a symbol across the project
- An agent on a smaller model gets lost in the repository structure
Not a fit when
- The project is small and the agent already sees all of it
- Your use is commercial and the PolyForm Noncommercial license does not fit
Example request
What breaks if I change the return type of UserService.validate?Limitations
PolyForm Noncommercial license; a paid enterprise edition exists for commercial use. On npm 11 npx may crash during install, and some grammars need a C++ toolchain or prebuilds. Embeddings are optional and fetch binaries from api.nuget.org, which may fail behind firewalls. Wiki generation needs an LLM provider key. Indexing large repos is memory-heavy.
How to disable. Remove the server with claude mcp remove gitnexus, delete GitNexus skills and hooks from .claude, and remove the .gitnexus folder in the project.
MCP
- Transport
- stdio
- Authentication
- not required
| Environment variables | |
|---|---|
| GITNEXUS_STORAGE_PATH | External directory for the index |
| GITNEXUS_SKIP_OPTIONAL_GRAMMARS | Set to 1 to skip building Dart, Proto, Swift and Kotlin grammars |
Security check
- Reads all project code and writes an index to disk
- Adds Claude Code hooks and edits AGENTS.md and CLAUDE.md
- The rename tool edits many files at once
README in short
The README opens with two commands: analyze builds the index and installs skills, setup wires MCP into editors. It explains the idea of precomputed structure so a tool returns full context in one call, and lists the MCP tools and resources. It covers install issues, indexing flags, embeddings, repository groups and Render deployment. The web UI and bridge mode with a local server are described separately.
FAQ
Is code sent to a server?
No, the CLI indexes locally and the web UI runs entirely in the browser.
Which agents are supported?
setup detects Claude Code, Cursor, Codex and others; Codex also has a plugin bundling MCP, skills and hooks.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything
Up-to-date, version-specific library docs and code examples in your agent's context, via MCP or a CLI plus skill