MCP SERVERGives an agent a real Android device over ADB — read the screen, tap, swipe, type, launch apps and run ADB commands.
LABSCO SUMMARY
How it reads the screen is the design decision that matters: text, structured elements and full XML are three separate tools, so checking that a button moved costs a snapshot_ui token and a detect_ui_change poll rather than a whole hierarchy dump. Settle the execution mode before you connect anything you care about — unrestricted is the default and grants full shell access, so set ADB_EXECUTION_MODE=restricted with an allowlist on a real device.
An MCP server that drives a connected Android device or emulator through ADB, with tools shaped to return small structured responses rather than raw XML dumps.
Python 3.11+, ADB installed on the host, and a device or emulator connected. It runs over stdio with uvx agent-droid-bridge; ADB_PATH points at the binary when adb is not on PATH. The security posture is set by environment variable: ADB_EXECUTION_MODE is unrestricted by default (all shell commands, with an optional ADB_SHELL_DENYLIST) or restricted (only what ADB_SHELL_ALLOWLIST names), ADB_ALLOW_SHELL=false blocks shell commands outright, and ADB_DENIED_TOOLS hides named tools at startup. ADB_EXTRA_TOOL_PACKS=app_manager loads the app-management pack, and MCP_LOG_ENABLED with MCP_LOG_DIR records every tool call and ADB command to JSONL.
One command — uvx agent-droid-bridge
USE CASES
Pull the tappable elements, tap the one you want, and type into the field it opens.
Take a snapshot token before the action, then poll until the screen content changes.
Get the visible text top-to-bottom, and a screenshot when the layout matters as much as the words.
See which devices ADB can reach, check what that device is and can do, then launch the app you want.
Run the command directly and read its output, within whatever your execution mode permits.
With the app_manager pack loaded, read the package details and copy the APK to the host.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
check_device_capabilitiesDevice capabilities and hardware profile for the connected Android device.
Use 'identity' to establish what device you are working with before starting a session. Use 'security' when a task requires root permissions or you need to confirm privilege level. Use 'hardware' when you need screen dimensions or memory constraints for layout decisions. Use 'all' only when you need a complete profile and latency is not a concern.
detect_ui_changePolls the UI hierarchy after an action and returns when the screen content changes or the timeout is reached. Returns changed status and elapsed time. By default, omits the XML hierarchy for efficiency — set return_hierarchy=True to receive the full hierarchy.
For efficient change detection: call snapshot_ui before the action, perform the action, then call detect_ui_change with baseline_token. Only use without baseline_token when you need to wait for a slow transition (loading screens, animations). Do not use to read the current screen state — use get_ui_hierarchy for that.
execute_adb_commandThe output of an ADB command. Parsed safely via shlex and never passed to a system shell.
get_screen_elementsStructured list of UI elements currently visible on the Android screen.
Returns elements filtered and shaped by the chosen mode. Prefer 'tappable' for navigation and 'interactive' when you need XPath or bounds for ADB commands. Only use 'all' as a last resort — it returns every node and can be large.
get_screen_textReturns all visible text on the current Android screen, sorted top-to-bottom.
Use this when you need to read what is on screen. Does not include coordinates or element info — for tapping or interacting, use get_screen_elements.
get_ui_hierarchyReturns the current Android screen as an XML UI hierarchy.
Use this when you need to locate element coordinates, read text, or find resource IDs to interact with. Do not call this after every action — only call it when you actually need to read screen content. To check if the screen changed after an action, use snapshot_ui before the action and detect_ui_change after.
launch_appAn Android app launched by its component name (package/activity).
list_devicesAll Android devices currently visible to ADB, with their serial numbers, connection state, and model names.
press_keyA key event sent to the Android device using the given keycode integer.
snapshot_uiTakes a lightweight snapshot of the current UI state and returns a short token.
Use this before performing an action (tap, swipe, launch, key press) when you only need to confirm the screen changed afterward — not read its content. Pass the returned token to detect_ui_change as baseline_token. This avoids loading the full XML hierarchy into context unnecessarily. Do not use this when you need to read or interact with screen elements — use get_ui_hierarchy for that.
swipe_screenA swipe gesture on the Android screen from (x1,y1) to (x2,y2) over the given duration.
take_screenshotA PNG screenshot of the current Android device screen with width, height, and base64-encoded image data.
tap_screenA tap gesture at the given pixel coordinates on the Android screen.
type_textText input into the currently focused Android input field.
Spaces are encoded automatically.
BEFORE YOU INSTALL
14 tools when we connected.
uvx on PATH
CONTEXT COST
Rated by the size of the 14 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
uvx agent-droid-bridge{
"servers": {
"agent-droid-bridge": {
"type": "stdio",
"command": "uvx",
"args": [
"agent-droid-bridge"
],
"env": {
"ADB_EXECUTION_MODE": "unrestricted",
"ADB_ALLOW_SHELL": "true",
"ADB_PATH": "adb",
"ADB_EXTRA_TOOL_PACKS": "",
"MCP_LOG_ENABLED": "false",
"MCP_LOG_DIR": "~/logs/agent-droid-bridge"
}
}
}
}git clone https://github.com/Neverlow512/agent-droid-bridge.git
cd agent-droid-bridge
python3.11 -m venv venv
venv/bin/pip install -e .If running from a local clone instead of uvx, use this command and args:
{
"mcpServers": {
"agent-droid-bridge": {
"command": "<YOUR_PATH_TO_AGENT_DROID_BRIDGE>/venv/bin/python",
"args": [
"-m",
"agent_droid_bridge.server"
],
"env": {
"PYTHONPATH": "<YOUR_PATH_TO_AGENT_DROID_BRIDGE>/src",
"ADB_EXECUTION_MODE": "unrestricted",
"ADB_ALLOW_SHELL": "true",
"ADB_PATH": "adb",
"ADB_EXTRA_TOOL_PACKS": "",
"MCP_LOG_ENABLED": "false",
"MCP_LOG_DIR": "~/logs/agent-droid-bridge"
}
}
}
}MCP servers
erichung9060
minhalvp
github-hewei
Nam0101