codegraph vs chrome-devtools-mcp
Two of the top mcp servers for developers, side by side: score, setup, license, activity and what each review found.
codegraph
Local code knowledge graph served to coding agents over MCP
chrome-devtools-mcp
MCP server that lets coding agents drive and debug a live Chrome
| What we compare | codegraph | chrome-devtools-mcp |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 92, widely used | 69, popular |
| Freshness | 100, active | 100, active |
| Maintenance | 91, healthy | 79, fair |
| Easy to run | 50, easy | 33, some setup |
| Agent-ready | 85, ready | 30, minimal |
| Facts from GitHub and the README | ||
| Stars | 73.7k | 53.3k |
| License | MIT (permissive) | Apache-2.0 (permissive) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | Oct 2026 | Sep 2026 |
| Language | C | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Mentioned | Not stated |
codegraph
CodeGraph indexes a project into a local graph of symbols, call edges and dependencies under `.codegraph/`, then exposes it to coding agents through an MCP server. Agents can fetch relevant source, call paths and change impact in one call instead of grepping and reading files. `codegraph install` wires it into Claude Code, Cursor, Codex CLI, opencode, Gemini CLI, Kiro, GitHub Copilot and others, and auto-sync keeps the index current.
Who it is for: Developers using AI coding agents on mid-to-large codebases
Strengths
- Runs locally; no Node.js needed, ships as a bundled installer or npm package
- One `codegraph install` configures MCP for nine named agents and IDEs
- Covers 30+ languages, including TypeScript, Python, Go, Rust, Java, C#, Swift
- Watches files and updates the graph automatically; no manual re-index
Weaknesses
- README admits about 80% more retrieval context stays resident in long sessions
- Published benchmarks are the author's, on 7 repos with one question each
- No Docker or compose setup; install is via curl/PowerShell script or npm
- Hosted CodeGraph platform is a waitlist product, separate from this repo
- no GPU
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)