mobile-use vs adb-mcp: Android emulator and device control over adb
mobile-use is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). adb-mcp: Android emulator and device control over adb is an MCP server published by iksnerd. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 |  mobile-use |  adb-mcp: Android emulator and device control over adb |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.25.0 Forks (GitHub): 4 Stars (GitHub): 18 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 | mobile-use | adb-mcp: Android emulator and device control over adb |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 18 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 4 (better) |
| Last release (differs) | Not published | 2026-11-07 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (ghcr.io/iksnerd/adb-mcp:0.25.0) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/microsoft/mobile-use | github.com/iksnerd/adb-mcp |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-11-09 | 2026-10-11 |
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
mobile-use
Observe and interact with explicitly selected real Android devices over authorized USB or paired wireless ADB.
adb-mcp: Android emulator and device control over adb
Drive an Android emulator or device over adb: screenshot, inspect UI, tap, type, build and test.
How to run each
mobile-use
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
adb-mcp: Android emulator and device control over adb As a local MCP server: Docker image
claude mcp add --transport stdio adb-mcp -- docker run -i --rm ghcr.io/iksnerd/adb-mcp:0.25.0Commands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: mobile-use · What it can do: adb-mcp: Android emulator and device control over adb · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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.