adb-android-control vs android-use
adb-android-control is a plugin bundle for AI coding tools published by hah23255. Marketplaces we read that list it: 1 (Community GitHub marketplaces). android-use is an MCP server published by GhostFaceModz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  adb-android-control |  android-use |
|---|---|---|
| Community marketplace hah23255/adb-android-control | Listed Version: not stated Forks (GitHub): 2 Stars (GitHub): 16 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | adb-android-control | android-use |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 16 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@ghostfacemodz/android-use) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 6, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/hah23255/adb-android-control | github.com/ghostfacemodz/android-adb-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen | 2026-10-20 | 2026-10-20 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
adb-android-control
Comprehensive Android device control via ADB (Android Debug Bridge). Use when user asks about: Android device management, app installation/uninstallation, APK operations, package management, file transfer (push/pull), screenshots, screen recording, input simulation (tap/swipe/text/keyevents), shell commands, logcat viewing, device info (battery/memory/storage), automation scripts, wireless ADB connection, scrcpy mirroring. Keywords: adb, android, phone, tablet, device, apk, install app, uninstall app, screenshot, screen record, tap, swipe, type text, keyevent, logcat, push file, pull file, shell, package, activity, intent, broadcast, dumpsys, getprop, settings, input, sendevent, monkey, am start, pm list, device info, battery status, wireless adb, connect device.
android-use
Let AI agents see and control an Android phone over ADB, with safety guards.
How to run each
adb-android-control As a Claude Code plugin
/plugin marketplace add hah23255/adb-android-control
/plugin install adb-android-control@adb-android-controlandroid-use As a local MCP server: npm package
claude mcp add --transport stdio android-use -- npx -y @ghostfacemodz/android-useCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of adb-android-control publish no settings it asks for, so we do not compare settings.
What it can do: adb-android-control · What it can do: android-use · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.