ADB MCP Tools

The android-debug-bridge MCP server exposes an Android device to the agent as tools. Every device-facing tool takes an optional device argument — a full serial, a serial prefix, a transport id or a model name — and defaults to ADB_SERIAL or the only connected device.

The same engine is available as the adb-agent CLI — see the adb-cli skill. Reach for the CLI when a flow is a straight sequence of steps you want to chain in one shell call; reach for these tools when you want images in the transcript and per-step reasoning.

Before the first action

Call list_devices. If it comes back empty, tell the user to start an emulator or connect a device with USB debugging enabled — do not keep trying other tools, they will all fail the same way. If it lists more than one device, the result says whether there is a default target; when there is none, pick one and pass device on every later call rather than letting each tool fail in turn.