chrome-devtools-mcp vs scientific-agent-skills
The two are close in size: 51.0k stars for chrome-devtools-mcp, 42.8k for scientific-agent-skills. Over the days we have tracked them chrome-devtools-mcp moved +8.4% and scientific-agent-skills +35.8%, so scientific-agent-skills is growing faster right now.
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work.
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
A large, curated collection of 148 domain-specific scientific Agent Skills with unified, provenance-rich access to 100+ scientific databases, packaged to plug into any Agent Skills–compatible host.
- Stars
- 42.8k
- Tracked growth
- +35.8%
- Maturity
- ●●●●●
- Last commit
- 2d ago
- Language
- Python
- License
- MIT
- Cost to run
- Free to install; uses your API key(s)
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 | scientific-agent-skills |
|---|---|---|
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 | ●●●●● Skills-only context |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● No noise controls | ●●●●● Docs guidance |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config flags available | ●●●●● Configurable skills |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable (opt-outs) | ●●●●● Self-hostable |
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 install |
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 scientific-agent-skills if…
Extensive scientific coverage — pick this when you need a maintained, ready-to-use library of validated skills and database connectors to turn your agent into a research assistant.
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.
K-Dense-AI/scientific-agent-skills
Questions people ask
Is chrome-devtools-mcp better than scientific-agent-skills?
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work. 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 scientific-agent-skills keeps my code private?
chrome-devtools-mcp: Self-hostable (opt-outs) (4/5). scientific-agent-skills: Self-hostable (4/5).
What does each one cost to run?
chrome-devtools-mcp: Free, runs locally. scientific-agent-skills: Free to install; uses your API key(s).
Full profiles: ChromeDevTools/chrome-devtools-mcp and K-Dense-AI/scientific-agent-skills. Everything else in Tools & MCP.