head to head · open source
chrome-devtools-mcp vs Avalonia
chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. Avalonia has 31,747 stars, 2,877 forks, 1,875 open issues and last shipped yesterday. chrome-devtools-mcp leads on adoption by 72% (54,665 vs 31,747 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; Avalonia is written in C# under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, Avalonia 9%. Avalonia 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 | Avalonia | |
|---|---|---|
| GitHub stars | ★ 55K | ★ 32K |
| License | Apache-2.0 | MIT |
| Written in | TypeScript | C# |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 5.3K | ⑂ 2.9K |
| 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 Avalonia if
- You want the Avalonia feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches C#
- You evaluated both and Avalonia 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 Avalonia
📖 About Avalonia is a cross platform UI framework for dotnet, providing a flexible styling system and supporting a wide range of platforms such as Windows, macOS, Linux, iOS, Android and WebAssembly. Avalonia is mature and production ready and is used by companies, including Schneider Electric, Unity, JetBrains and GitHub. Considered by many to be the spiritual successor to WPF, Avalonia UI provides a familiar, modern development experience for XAML developers creating cross platform applications. While Avalonia UI is similar to WPF, it isn't a 1:1 copy, and you'll find plenty of improvements. For those seeking…
read the full Avalonia 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 Avalonia more popular?
chrome-devtools-mcp has 54,665 GitHub stars and Avalonia has 31,747. chrome-devtools-mcp has the larger community by that measure.
Are chrome-devtools-mcp and Avalonia free?
Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and Avalonia under MIT. Neither carries a licence fee.
What is the difference between chrome-devtools-mcp and Avalonia?
chrome-devtools-mcp is written in TypeScript and Avalonia in C#. 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 Avalonia?
Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose Avalonia if its feature set, stack or MIT licence fits better. Both are self-hostable.