head to head · open source
chrome-devtools-mcp vs NooBox
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. NooBox has 522 stars, 54 forks, 37 open issues and last shipped 12 months ago. chrome-devtools-mcp leads on adoption by 10,372% (54,665 vs 522 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; NooBox is written in TypeScript under GPL-3.0. chrome-devtools-mcp has attracted 10% as many forks as stars, NooBox 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 | NooBox | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 522 |
| License | Apache-2.0 | GPL-3.0 |
| Written in | TypeScript | TypeScript |
| Last push | 2026-11-02 | 2025-11-21 |
| Forks | ⑂ 5.3K | ⑂ 54 |
| 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 NooBox if
- You want the NooBox feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches TypeScript
- You evaluated both and NooBox 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 NooBox
Noobox 二箱(简) 二箱(繁) Table Of Content Installation Functionalities Search By Image Extract Images Auto Refresh HTML5 Video Control (Abort) License Language Installation Chrome Web Stroe CRX Download How to Install CRX ? Setting More Tools Extension Open Developer Mode Drag CRX File Search By Image "If you’ve stumbled across an image on the internet—perhaps on your favorite social media site—and you want to know more about it, you can always ask the person responsible for the post. Odds are good that they probably just cribbed the image from somewhere else, and don’t know any more about where it came from. But…
read the full NooBox 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 NooBox more popular?
chrome-devtools-mcp has 54,665 GitHub stars and NooBox has 522. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and NooBox free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and NooBox under GPL-3.0. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and NooBox?
chrome-devtools-mcp is written in TypeScript and NooBox 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 NooBox?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose NooBox if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.