head to head · open source
chrome-devtools-mcp vs chrome-remote-interface
chrome-devtools-mcp has 52,222 GitHub stars, 4,037 forks, 109 open issues and last shipped yesterday. chrome-remote-interface has 4,553 stars, 322 forks, 12 open issues and last shipped 7 months ago. chrome-devtools-mcp leads on adoption by 1,047% (52,222 vs 4,553 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 8% 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 13541 open source comparisons
Side by side
| chrome-devtools-mcp | chrome-remote-interface | |
|---|---|---|
| GitHub stars | ★ 52K | ★ 4.6K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | JavaScript |
| Last push | 2026-09-18 | 2026-02-09 |
| Forks | ⑂ 4.0K | ⑂ 322 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick chrome-devtools-mcp if
- You weight community size — 52K 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 mcp is an Apache 2.0 TypeScript Model Context Protocol server, distributed on npm, that gives coding agents such as Claude, Cursor, Copilot and Antigravity control over and visibility into a live Chrome browser through the full Chrome DevTools toolset.
read the full chrome-devtools-mcp overview →
About chrome-remote-interface
chrome remote interface is an MIT licensed JavaScript library that gives Node.js applications a straightforward API for the Chrome Debugging Protocol, so they can instrument Chrome and other protocol compatible runtimes without handling raw protocol messages.
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 52,222 GitHub stars and chrome-remote-interface has 4,553. 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 (52,222 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.