chrome-devtools-mcp vs codebase-memory-mcp
Two of the top mcp servers for developers, side by side: score, setup, license, activity and what each review found.
chrome-devtools-mcp
MCP server that lets coding agents drive and debug a live Chrome
codebase-memory-mcp
MCP server that indexes codebases into a queryable knowledge graph
| What we compare | chrome-devtools-mcp | codebase-memory-mcp |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 69, popular | 47, known |
| Freshness | 100, active | 100, active |
| Maintenance | 79, fair | 81, healthy |
| Easy to run | 33, some setup | 50, easy |
| Agent-ready | 30, minimal | 0, none |
| Facts from GitHub and the README | ||
| Stars | 53.3k | 46.3k |
| License | Apache-2.0 (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | Sep 2026 | Sep 2026 |
| Language | TypeScript | C |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Mentioned |
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)
codebase-memory-mcp
A native C executable that parses repositories with tree-sitter (162 languages) into a persistent graph of functions, classes, call chains, HTTP routes and cross-service links, and exposes it through 17 MCP tools. It adds semantic search with bundled embeddings, Cypher-like queries, dead code detection, git diff impact mapping and a built-in 3D graph UI. Processing is local, and `install` configures detected coding-agent clients.
Who it is for: Developers giving coding agents structural code search over local repos
Strengths
- Runs locally with no API key, hosted service or language runtime
- Bundled embeddings enable semantic search without Ollama or Docker
- Covers 162 languages; Hybrid LSP type resolution for 10 of them
- Releases are VirusTotal-scanned and SLSA 3 attested
Weaknesses
- Updates require re-running the install script; `update` only prints the command
- Defender may flag release binaries as a false positive, per the README
- All active processes must share the exact same build and cache root
- Watcher covers only git projects opened in MCP sessions, by default
- no GPU
- Models: nomic-embed-code (bundled, int8, 768d)
- port 9749