Android over adb

Lets an assistant see and control Android phones and emulators over adb, without installing anything on the device.

What you can do

Connects to Android devices and emulators through adb and exposes the screen as a short list of visible text and touchable elements with their centre, type, id and state. The assistant can tap elements by name, tap or swipe coordinates, type text, press keys, take screenshots, list and launch apps, install APKs, and read recent logcat output per app. There is deliberately no free shell tool; every action is named and bounded.

When to use it

Useful for testing your own app the way a user would and reading the resulting crash in logcat, for repetitive phone chores such as changing notification settings, and for accessibility scenarios where a screen is described and acted on by voice. It suits anyone who wants an assistant to drive a real Android device or emulator.

Requirements

Runs as a local process on the user's machine, installed from PyPI as android-mcp-lite and started with uvx or pip. The phone or emulator must have USB or wireless debugging enabled and be visible to adb; platform-tools must be installed. With several devices, pass the serial from devices to each tool. Set ADB if adb is not on the PATH or in ~/Android/Sdk/platform-tools. Desktop only.