head to head · open source
chrome-devtools-mcp vs parchi
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. parchi has 546 stars, 57 forks, 11 open issues and last shipped 4 days ago. chrome-devtools-mcp leads on adoption by 9,912% (54,665 vs 546 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; parchi is written in TypeScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, parchi 10%. chrome-devtools-mcp was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| chrome-devtools-mcp | parchi | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 546 |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2026-10-30 |
| Forks | ⑂ 5.3K | ⑂ 57 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick chrome-devtools-mcp if
- You weight community size — 55K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick parchi if
- You want the parchi feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and parchi fits your workflow better
About chrome-devtools-mcp
Chrome DevTools for agents Chrome DevTools for agents ( chrome devtools mcp ) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It acts as a Model Context Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in depth debugging, and performance analysis. A [CLI][cli] is also provided for use without MCP. [Tool reference][tool reference] [Changelog][changelog] [Contributing][contributing] [Troubleshooting][troubleshooting] [Design Principles][design principles] Key features Get…
read the full chrome-devtools-mcp overview →
About parchi
Parchi AI powered browser copilot (Chrome/Firefox extension). Chat driven browser automation in a side panel: navigate, read, click, type, extract, and summarize. ⚠️ Safety Notice Browser automation can perform sensitive actions on your behalf. Use this tool only if you understand and accept the risks: automation may violate site terms of service prompt injection can cause unsafe actions sensitive information can be exposed if you run untrusted prompts/pages Always review model output and keep strict tool/domain controls enabled when needed. 📦 Installation Chrome (recommended) Then: 1. Open chrome://extensions…
read the full parchi overview →
More in Productivity & Utilities
Related comparisons
More Browsers & Extensions projects
Compare either of these against the rest of the Browsers & Extensions field.
Frequently asked questions
Is chrome-devtools-mcp or parchi more popular?
chrome-devtools-mcp has 54,665 GitHub stars and parchi has 546. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and parchi free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and parchi under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and parchi?
chrome-devtools-mcp is written in TypeScript and parchi in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, chrome-devtools-mcp or parchi?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose parchi if its feature set, stack or MIT licence fits better. Both are self-hostable.