Home/Compare/chrome-devtools-mcp vs Android-MCP

Comparison

chrome-devtools-mcp vs Android-MCP

Verdict

Pick chrome-devtools-mcp if chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript; pick Android-MCP if android-MCP is a Python-based server for interacting with Android devices designed to ease development tasks that require automation and interaction through a dedicated MCP server.

Markdown twin · chrome-devtools-mcp alternatives · Android-MCP alternatives

GraphCanon updated Aug 25, 2026

15views this month

chrome-devtools-mcp logo

chrome-devtools-mcp

ChromeDevTools/chrome-devtools-mcp

50kpushed Aug 25, 2026
vs
Android-MCP logo

Android-MCP

CursorTouch/Android-MCP

805pushed Jul 1, 2026

Trust & integrity

Signalchrome-devtools-mcpAndroid-MCP
Maintenance
Very active (0d since push)
As of Aug 25, 2026 · github_public_v1
Steady (41d since push)
As of Aug 12, 2026 · github_public_v1
Provenance
Not a fork · Organization account
As of Aug 25, 2026 · github_public_v1
Not a fork · Organization account
As of Aug 12, 2026 · github_public_v1
OSV dependency advisories
No lockfile (source not queried)
As of Jul 11, 2026 · osv@v1
No lockfile (source not queried)
As of Jul 19, 2026 · osv@v1
deps.dev advisories
Not queried
deps.dev@v1
Not queried
deps.dev@v1
OpenSSF Scorecard
Not queried
openssf-scorecard@v1
No public record from this source
As of Sep 6, 2026 · openssf-scorecard@v1

Tagline

chrome-devtools-mcp
Developer tools to enhance coding efficiency and debugging capabilities
Android-MCP
MCP Server for interacting with Android Devices

Stars

chrome-devtools-mcp
50k
Android-MCP
805

Forks

chrome-devtools-mcp
3.5k
Android-MCP
110

Open issues

chrome-devtools-mcp
90
Android-MCP
8

Language

chrome-devtools-mcp
TypeScript
Android-MCP
Python

Adopt for

chrome-devtools-mcp
chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.
Android-MCP
Android-MCP is a Python-based server for interacting with Android devices designed to ease development tasks that require automation and interaction through a dedicated MCP server.

Persona

chrome-devtools-mcp
-
Android-MCP
-

Runtime

chrome-devtools-mcp
-
Android-MCP
-

License

chrome-devtools-mcp
Apache-2.0
Android-MCP
MIT

Last pushed

chrome-devtools-mcp
Aug 25, 2026
Android-MCP
Jul 1, 2026

Categories

chrome-devtools-mcp
Developer Tools
Android-MCP
Developer Tools

Trust and health

Maintenance

chrome-devtools-mcp
Very active (96%)
Android-MCP
Steady (60%)

Days since push

chrome-devtools-mcp
0d
Android-MCP
41d

Open issues (now)

chrome-devtools-mcp
90
Android-MCP
8

Stars delta

chrome-devtools-mcp
+2.1k (30d)
Android-MCP
Unknown

Open issues delta

chrome-devtools-mcp
-21 (30d)
Android-MCP
Unknown

OpenSSF Scorecard

chrome-devtools-mcp
Not queried
Android-MCP
No public record from this source

Full report

chrome-devtools-mcp
Trust report
Android-MCP
Trust report

Choose chrome-devtools-mcp if…

  • chrome-devtools-mcp is primarily TypeScript; Android-MCP is Python.
  • License: chrome-devtools-mcp is Apache-2.0, Android-MCP is MIT.
  • Tags unique to chrome-devtools-mcp: browser, chrome, chrome-devtools, debugging.
  • chrome-devtools-mcp ships an MCP server manifest.
  • - When your project is heavily dependent on browser interactions and requires advanced debugging capabilities specific to Chrome

When NOT to use chrome-devtools-mcp

  • - If your development environment does not revolve around Chrome or if browser compatibility across different browsers is a primary concern
  • - When you are working on non-TypeScript projects, as this tool may not provide the same level of utility and customization options

Choose Android-MCP if…

  • Android-MCP is primarily Python; chrome-devtools-mcp is TypeScript.
  • License: Android-MCP is MIT, chrome-devtools-mcp is Apache-2.0.
  • Tags unique to Android-MCP: ai, android, automation.
  • When developing applications requiring close integration with the Android device's hardware and needing an automated testing framework

When NOT to use Android-MCP

  • If your project requires extensive use of native Java or Kotlin for deep system interactions that cannot leverage Python effectively
  • In scenarios demanding very lightweight server solutions, as Android-MCP might introduce additional overhead due to its full-feature set

Explore

Sources

Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.

GitHub stars on cards: chrome-devtools-mcp 50k · Android-MCP 805 (synced Aug 25, 2026).

Common questions

What is the difference between chrome-devtools-mcp and Android-MCP?
chrome-devtools-mcp: Developer tools to enhance coding efficiency and debugging capabilities. Android-MCP: MCP Server for interacting with Android Devices. See the comparison table for live GitHub stats and shared categories.
When should I choose chrome-devtools-mcp over Android-MCP?
Choose chrome-devtools-mcp over Android-MCP when chrome-devtools-mcp is primarily TypeScript; Android-MCP is Python; License: chrome-devtools-mcp is Apache-2.0, Android-MCP is MIT; Tags unique to chrome-devtools-mcp: browser, chrome, chrome-devtools, debugging; chrome-devtools-mcp ships an MCP server manifest; - When your project is heavily dependent on browser interactions and requires advanced debugging capabilities specific to Chrome.
When should I choose Android-MCP over chrome-devtools-mcp?
Choose Android-MCP over chrome-devtools-mcp when Android-MCP is primarily Python; chrome-devtools-mcp is TypeScript; License: Android-MCP is MIT, chrome-devtools-mcp is Apache-2.0; Tags unique to Android-MCP: ai, android, automation; When developing applications requiring close integration with the Android device's hardware and needing an automated testing framework.
When should I avoid chrome-devtools-mcp?
- If your development environment does not revolve around Chrome or if browser compatibility across different browsers is a primary concern - When you are working on non-TypeScript projects, as this tool may not provide the same level of utility and customization options
When should I avoid Android-MCP?
If your project requires extensive use of native Java or Kotlin for deep system interactions that cannot leverage Python effectively In scenarios demanding very lightweight server solutions, as Android-MCP might introduce additional overhead due to its full-feature set
Is chrome-devtools-mcp or Android-MCP more popular on GitHub?
chrome-devtools-mcp has more GitHub stars (49,700 vs 805). Stars measure visibility, not whether either tool fits your constraints.
Are chrome-devtools-mcp and Android-MCP open source?
Yes - both are open-source projects on GitHub (chrome-devtools-mcp: Apache-2.0, Android-MCP: MIT).
Where can I find alternatives to chrome-devtools-mcp or Android-MCP?
GraphCanon lists graph-backed alternatives at chrome-devtools-mcp alternatives and Android-MCP alternatives (chrome-devtools-mcp markdown twin, Android-MCP markdown twin), ranked by typed relationship edges rather than popularity votes.
Is there a machine-readable version of this comparison?
Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
Which is better maintained, chrome-devtools-mcp or Android-MCP?
chrome-devtools-mcp: Very active. Android-MCP: Steady. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
Where are the full trust reports for chrome-devtools-mcp and Android-MCP?
GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: chrome-devtools-mcp trust report; Android-MCP trust report.

Was this helpful?

Anonymous feedback helps us improve pages and translations.