gitnexus vs chrome-devtools-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
chrome-devtools-mcp
MCP server that lets coding agents drive and debug a live Chrome
Verdict
gitnexus ranks higher, 89 to 70. Of the 5 score parts we measure for both, gitnexus leads on 3, chrome-devtools-mcp on 1 and 1 is even.
- Adoptionchrome-devtools-mcp leads by 8 points, 85 to 77.
- FreshnessEven at 100.
- Maintenancegitnexus leads by 6 points, 92 to 86.
- Easy to rungitnexus leads by 50 points, 83 to 33: a wide gap.
- Agent-readygitnexus leads by 70 points, 100 to 30: 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 chrome-devtools-mcp if you are
Developers who want their coding agent to debug and test pages in Chrome
- Records DevTools performance traces and extracts insights from them
- Puppeteer-based automation waits for action results automatically
| What we compare | gitnexus | chrome-devtools-mcp |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 77, popular | 85, widely used |
| Freshness | 100, active | 100, active |
| Maintenance | 92, healthy | 86, healthy |
| Easy to run | 83, very easy | 33, some setup |
| Agent-ready | 100, ready | 30, minimal |
| Facts from GitHub and the README | ||
| Stars | 47.9k | 53.6k |
| License | custom license (read the license) | Apache-2.0 (permissive) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | Sep 2026 | Sep 2026 |
| Language | TypeScript | TypeScript |
| Docker | Yes | No |
| 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
chrome-devtools-mcp
chrome-devtools-mcp is an MCP server that gives coding agents such as Claude, Cursor and Copilot control of a live Chrome browser. It records performance traces through Chrome DevTools, inspects network requests and console messages with source-mapped stack traces, and automates page actions via puppeteer. A CLI is included for use without MCP, and a --slim mode exposes a smaller tool set.
Who it is for: Developers who want their coding agent to debug and test pages in Chrome
Strengths
- Records DevTools performance traces and extracts insights from them
- Puppeteer-based automation waits for action results automatically
- Slim mode limits the exposed tools to basic browser tasks
- Also ships a CLI for use without an MCP client
Weaknesses
- Usage statistics are sent to Google by default; opt out with --no-usage-statistics
- Performance tools may send trace URLs to the Google CrUX API
- Officially supports only Chrome and Chrome for Testing
- Exposes all browser content to the connected MCP client
- no GPU
- Needs Node.js LTS, npm, Google Chrome (current stable)
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.