chrome-devtools-mcp vs servers
The two are close in size: 51.0k stars for chrome-devtools-mcp, 90.1k for servers. Over the days we have tracked them chrome-devtools-mcp moved +8.4% and servers +1.5%, so chrome-devtools-mcp is growing faster right now.
servers leads on context depth and noise control. chrome-devtools-mcp does not take any axis by a clear margin.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Exposes the full Chrome DevTools over MCP so agents can control and inspect a live Chrome instance for automation, deep debugging, and performance analysis.
- Stars
- 51.0k
- Tracked growth
- +8.4%
- Maturity
- ●●●●●
- Last commit
- 14h ago
- Language
- TypeScript
- License
- Apache-2.0
- Cost to run
- Free, runs locally
Provides official, multi-language reference implementations of the Model Context Protocol that showcase how to give LLMs secure, controlled access to tools and data.
- Stars
- 90.1k
- Tracked growth
- +1.5%
- Maturity
- ●●●●●
- Last commit
- 2d ago
- Language
- TypeScript
- License
- NOASSERTION
- Cost to run
- Free to run locally
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | chrome-devtools-mcp | servers |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Browser-only context | ●●●●● Diff + related files |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● No noise controls | ●●●●● Configurable access controls |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config flags available | ●●●●● Configurable CLI & SDK |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable (opt-outs) | ●●●●● Runs fully local |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Bring-your-own model | ●●●●● Bring-your-own-key |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command start | ●●●●● One-command start |
Which one to pick
Pick chrome-devtools-mcp if…
Advanced browser debugging — use this when you need an agent to interact with and inspect a live Chrome browser for reliable automation, debugging, and performance traces.
Pick servers if…
Reference implementations — run ready-made, multi-language example MCP servers locally with a single command to prototype integrations and learn best practices.
- Context depth: Diff + related files (3/5 against 1/5)
- Noise control: Configurable access controls (3/5 against 1/5)
What people want from each one
ChromeDevTools/chrome-devtools-mcp
Hacker News: ChromeDevTools/Chrome-devtools-MCP: Chrome DevTools for coding agents drew 11 points and 0 comments.
modelcontextprotocol/servers
Questions people ask
Is chrome-devtools-mcp better than servers?
servers leads on context depth and noise control. chrome-devtools-mcp does not take any axis by a clear margin. chrome-devtools-mcp is worth picking when advanced browser debugging — use this when you need an agent to interact with and inspect a live Chrome browser for reliable automation, debugging, and performance traces.
Which of chrome-devtools-mcp and servers keeps my code private?
chrome-devtools-mcp: Self-hostable (opt-outs) (4/5). servers: Runs fully local (5/5).
What does each one cost to run?
chrome-devtools-mcp: Free, runs locally. servers: Free to run locally.
Full profiles: ChromeDevTools/chrome-devtools-mcp and modelcontextprotocol/servers. Everything else in Tools & MCP.