head to head · open source
chrome-devtools-mcp vs chrome-remote-interface
chrome-devtools-mcp has 54,739 GitHub stars, 5,254 forks, 109 open issues and last shipped yesterday. chrome-remote-interface has 4,558 stars, 324 forks, 12 open issues and last shipped 9 months ago. chrome-devtools-mcp leads on adoption by 1,101% (54,739 vs 4,558 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; chrome-remote-interface is written in JavaScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, chrome-remote-interface 7%. chrome-devtools-mcp was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (browser), so they are genuine substitutes rather than adjacent tools.
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 | chrome-remote-interface | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 4.6K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | JavaScript |
| Last push | 2026-11-03 | 2026-02-09 |
| Forks | ⑂ 5.3K | ⑂ 324 |
| 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 chrome-remote-interface if
- You want the chrome-remote-interface feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches JavaScript
- You evaluated both and chrome-remote-interface 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 chrome-remote-interface
chrome remote interface [Chrome Debugging Protocol] interface that helps to instrument Chrome (or any other suitable implementation) by providing a simple abstraction of commands and notifications using a straightforward JavaScript API. Sample API usage The following snippet loads and dumps every request made: Find more examples in the [wiki]. You may also want to take a look at the [FAQ]. [wiki]: [async await example]: [FAQ]: Installation npm install chrome remote interface Install globally ( g ) to just use the bundled client. Implementations This module should work with every application implementing the…
read the full chrome-remote-interface 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 chrome-remote-interface more popular?
chrome-devtools-mcp has 54,739 GitHub stars and chrome-remote-interface has 4,558. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and chrome-remote-interface free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and chrome-remote-interface under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and chrome-remote-interface?
chrome-devtools-mcp is written in TypeScript and chrome-remote-interface in JavaScript. 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 chrome-remote-interface?
Choose chrome-devtools-mcp if you want the larger community (54,739 stars) or its Apache-2.0 licence terms. Choose chrome-remote-interface if its feature set, stack or MIT licence fits better. Both are self-hostable.