head to head · open source

chrome-devtools-mcp vs Thorium-Android

chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. Thorium-Android has 802 stars, 14 forks, 13 open issues and last shipped 23 days ago. chrome-devtools-mcp leads on adoption by 6,716% (54,665 vs 802 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; Thorium-Android is written in various languages under BSD-3-Clause. chrome-devtools-mcp has attracted 10% as many forks as stars, Thorium-Android 2%. 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.

chrome-devtools-mcp ★ 55K Thorium-Android ★ 802 category Productivity & Utilities

← all 20902 open source comparisons

Side by side

chrome-devtools-mcp Thorium-Android
GitHub stars ★ 55K ★ 802
License Apache-2.0 BSD-3-Clause
Written in TypeScript —
Last push 2026-11-02 2026-10-11
Forks ⑂ 5.3K ⑂ 14
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

full chrome-devtools-mcp profile →

pick Thorium-Android if

  • You want the Thorium-Android feature set and don't need the biggest community
  • You prefer the BSD-3-Clause license terms
  • You evaluated both and Thorium-Android fits your workflow better

full Thorium-Android profile →

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 Thorium-Android

Thorium Browser for Android – Simply a seperate repo to serve builds of Thorium for Android. Both arm32 and arm64 are supported. The main repo (and Linux builds) are located at Thanks for using Thorium!

read the full Thorium-Android 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 Thorium-Android more popular?

chrome-devtools-mcp has 54,665 GitHub stars and Thorium-Android has 802. chrome-devtools-mcp has the larger community by that measure.

Are chrome-devtools-mcp and Thorium-Android free?

Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and Thorium-Android under BSD-3-Clause. Neither carries a licence fee.

What is the difference between chrome-devtools-mcp and Thorium-Android?

chrome-devtools-mcp is written in TypeScript and Thorium-Android in various languages. 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 Thorium-Android?

Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose Thorium-Android if its feature set, stack or BSD-3-Clause licence fits better. Both are self-hostable.