head to head · open source
chrome-devtools-mcp vs cli
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. cli has 32,064 stars, 1,978 forks, 131 open issues and last shipped 4 days ago. chrome-devtools-mcp leads on adoption by 70% (54,665 vs 32,064 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; cli is written in Rust under Apache-2.0. chrome-devtools-mcp has attracted 10% as many forks as stars, cli 6%. 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 | cli | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 32K |
| License | Apache-2.0 | Apache-2.0 |
| Written in | TypeScript | Rust |
| Last push | 2026-11-02 | 2026-10-30 |
| Forks | ⑂ 5.3K | ⑂ 2.0K |
| 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 cli if
- You want the cli feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Rust
- You evaluated both and cli 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 cli
gws One CLI for all of Google Workspace — built for humans and AI agents. Drive, Gmail, Calendar, and every Workspace API. Zero boilerplate. Structured JSON output. 40+ agent skills included. [!NOTE] This is not an officially supported Google product. ⬇️ Download the latest release for your OS gws doesn't ship a static list of commands. It reads Google's own Discovery Service at runtime and builds its entire command surface dynamically. When Google Workspace adds an API endpoint or method, gws picks it up automatically. [!IMPORTANT] This project is under active development. Expect breaking changes as we march…
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 cli more popular?
chrome-devtools-mcp has 54,665 GitHub stars and cli has 32,064. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and cli free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and cli under Apache-2.0. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and cli?
chrome-devtools-mcp is written in TypeScript and cli in Rust. 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 cli?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose cli if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.