head to head · open source
chrome-devtools-mcp vs mue
chrome-devtools-mcp has 54,631 GitHub stars, 5,246 forks, 109 open issues and last shipped 2 days ago. mue has 772 stars, 89 forks, 26 open issues and last shipped 10 days ago. chrome-devtools-mcp leads on adoption by 6,977% (54,631 vs 772 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; mue is written in JavaScript under BSD-3-Clause. chrome-devtools-mcp has attracted 10% as many forks as stars, mue 12%. 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 (chrome), 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 | mue | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 772 |
| License | Apache-2.0 | BSD-3-Clause |
| Written in | TypeScript | JavaScript |
| Last push | 2026-11-01 | 2026-10-24 |
| Forks | ⑂ 5.2K | ⑂ 89 |
| 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 mue if
- You want the mue feature set and don't need the biggest community
- You prefer the BSD-3-Clause license terms
- Your stack matches JavaScript
- You evaluated both and mue 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 mue
Mue A fast, open and free to use browser extension that gives a new, fresh and customisable tab page to modern browsers. muetab.com 🤔 Why Mue? Beautiful and Minimalist Design Customisable Layout Widgets (such as weather, notes, bookmarks and more) Privacy Focused does not track your browsing activity Extensible with the Mue Marketplace Open Source under the BSD 3 License 🌶️ Installation Mue can be downloaded on the following browsers: Chrome Edge Firefox Whale and can be manually sideloaded on others using the files on GitHub Releases 🚀 Demo A fully featured demo of the tab extension is available in browser…
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 mue more popular?
chrome-devtools-mcp has 54,631 GitHub stars and mue has 772. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and mue free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and mue under BSD-3-Clause. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and mue?
chrome-devtools-mcp is written in TypeScript and mue 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 mue?
Choose chrome-devtools-mcp if you want the larger community (54,631 stars) or its Apache-2.0 licence terms. Choose mue if its feature set, stack or BSD-3-Clause licence fits better. Both are self-hostable.