Let Claude see and drive an Android phone over adb (MCP server)
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"android-mcp-lite","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# android-mcp <!-- mcp-name: io.github.ouchi-dev/android-mcp --> Let Claude, or any [MCP](https://modelcontextprotocol.io) assistant, see an Android phone's screen and use it, over plain `adb`. No app to install on the phone, no root. *Laisser Claude voir l'écran d'un téléphone Android et s'en servir, par adb, sans rien installer sur le téléphone.* What it is good for: - **Testing your own app** like a user would: *"open my app, create an account, tell me where it breaks"*, then read the crash in `logcat`. - **Repetitive phone chores**: *"go through my notifications settings and turn off every shopping app"*. - **Accessibility**: describing a screen and acting on it by voice through the assistant. ## How it sees the screen `screen_elements` turns the phone's accessibility tree into a short list: every visible text and every touchable element, with its centre, type, id and state (checked, disabled, editable...). The assistant then taps by name with `tap_element("Wi-Fi")`. That is cheaper and much more reliable than guessing coordinates on a screenshot; `screenshot` is there for layout, images and games. ## Tools | Tool | | |---|---| | `devices` | Phones and emulators adb can see | | `screen_elements`, `screenshot`, `current_app` | Read the screen | | `tap_element`, `tap`, `swipe`, `type_text`, `press_key` | Act on it | | `list_apps`, `launch_app`, `install_apk` | Apps | | `logcat` | Recent log, per app, errors only if wanted | There is deliberately **no free shell tool**: every action is named and bounded, and the server's instructions ask the assistant to check with you before sending messages, paying or deleting anything. ## Install 1. On the phone: *Settings > About > tap Build number 7 times*, then *Developer options > USB debugging* (or *Wireless debugging*). Plug it in and accept the prompt. 2. On the computer, with [platform-tools](https://developer.android.com/tools/releases/platform-tools) installed (`adb devices` should list the phone…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.