gitnexus vs n8n-mcp
Two of the top projects in MCP servers for developers, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.
gitnexus
Code knowledge graph exposed to coding agents through MCP tools
n8n-mcp
MCP server exposing n8n node docs, templates and workflow management to AI assistants
Verdict
gitnexus ranks higher, 91 to 76. Of the 5 score parts we measure for both, gitnexus leads on 3, n8n-mcp on 1 and 1 is even.
- Adoptiongitnexus leads by 18 points, 88 to 70: a wide gap.
- FreshnessEven at 100.
- Maintenancen8n-mcp leads by 1 point, 93 to 92: close to even.
- Easy to rungitnexus leads by 33 points, 83 to 50: a wide gap.
- Agent-readygitnexus leads by 30 points, 100 to 70: a wide gap.
Pick gitnexus if you are
Developers giving Claude Code, Cursor or Codex repo-wide dependency context
- Precomputes clusters and processes at index time, so impact returns callers and confidence in one call
- One analyze command indexes, installs skills, registers Claude Code hooks and writes AGENTS.md/CLAUDE.md
Pick n8n-mcp if you are
Developers building n8n workflows with Claude, Cursor or other MCP clients
- Node, template and validation tools (search_nodes, get_node, validate_workflow) cover core and community nodes
- 21 management tools create, patch, autofix and test workflows on a connected n8n instance
| What we compare | gitnexus | n8n-mcp |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 88, widely used | 70, popular |
| Freshness | 100, active | 100, active |
| Maintenance | 92, healthy | 93, healthy |
| Easy to run | 83, very easy | 50, easy |
| Agent-ready | 100, ready | 70, partly |
| Facts from GitHub and the README | ||
| Stars | 47.9k | 23.1k |
| License | custom license (read the license) | MIT (permissive) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | Sep 2026 | Oct 2026 |
| Language | TypeScript | TypeScript |
| Docker | Yes | Yes |
| GPU | Optional | Not needed |
| arm64 or Apple Silicon | Mentioned | Not stated |
gitnexus
GitNexus indexes a repository with Tree-sitter into a LadybugDB graph of dependencies, call chains, clusters and execution flows. It serves that graph to agents such as Claude Code, Cursor and Codex through 19 MCP tools (impact, trace, query, rename, cypher and others), and installs skills and hooks. A browser Web UI offers graph exploration and chat.
Who it is for: Developers giving Claude Code, Cursor or Codex repo-wide dependency context
Strengths
- Precomputes clusters and processes at index time, so impact returns callers and confidence in one call
- One analyze command indexes, installs skills, registers Claude Code hooks and writes AGENTS.md/CLAUDE.md
- setup auto-detects editors; Claude Code and Codex get MCP, skills and pre/post tool hooks
- CLI indexing runs locally with native Tree-sitter and persistent LadybugDB storage
Weaknesses
- PolyForm Noncommercial license restricts commercial use
- Web UI in-browser mode is limited to about 5k files
- npx install can crash on npm 11; some grammars need a C++ toolchain or are skipped
- Render deploy costs about $35/month and the token is the only access control
- GPU optional
- Docker + Compose
- Needs Node.js, LadybugDB, Tree-sitter
- Models: Claude Code, Cursor, Codex, Antigravity, Windsurf
n8n-mcp
n8n-MCP is a TypeScript MCP server that gives AI assistants searchable access to 3,135 n8n nodes (840 core, 2,295 community), their property schemas, and 2,352 workflow templates. With an n8n API URL and key configured, it also creates, updates, validates, tests and deploys workflows on a live n8n instance. It can be used through a hosted dashboard or self-hosted via npx, Docker or Railway.
Who it is for: Developers building n8n workflows with Claude, Cursor or other MCP clients
Strengths
- Node, template and validation tools (search_nodes, get_node, validate_workflow) cover core and community nodes
- 21 management tools create, patch, autofix and test workflows on a connected n8n instance
- Hosted option with free tier of 100 tool calls/day, or self-host via npx, Docker or Railway
- Setup guides for Claude Code, Cursor, VS Code, Windsurf and Codex
Weaknesses
- Operation coverage is 66.5% and docs coverage 86%, so some nodes lack detail
- Management tools need N8N_API_URL and N8N_API_KEY; some also need a separate MCP access token
- README warns AI edits to production workflows are unpredictable; backups needed
- Split-host n8n instance-level MCP (N8N_MCP_BASE_URL) is not supported
- no GPU
- Docker + Compose
- Needs n8n instance (optional, for management tools), n8n API key
More in MCP servers for developers
Building with these?
We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.