What is adb-mcp?

adb-mcp is a server that connects AI agents to Android devices and emulators through a protocol called MCP (Model Context Protocol). Android Debug Bridge, or ADB, is the standard command-line toolkit for communicating with Android phones, tablets, and virtual devices, adb-mcp wraps nearly all of ADB's capabilities into structured tools that agents can call directly. The problem it solves: automating an Android device normally requires knowing specific ADB command syntax. adb-mcp removes that requirement by exposing every common ADB operation as a named, typed function. An agent can take a screenshot, install an app, tap the screen, capture logs, reboot the device, inspect installed packages, or run shell commands, all without constructing raw ADB strings. For anything the built-in tools don't cover, a raw adb_command escape hatch is available. The tool groups cover a wide surface: device discovery and connection, shell execution and system properties, app install and package management, file transfer, screen capture and recording, logcat and bug reports, input simulation, network and port management, and emulator console control. To run it you need Node.js 20 or newer and Android Platform Tools already installed, with the adb binary on your system path. You build the server from TypeScript source, then register it in your MCP client's configuration. From that point, any MCP-compatible AI agent can control connected Android devices as part of its workflow. It is written in TypeScript and is intended for use with test devices or emulators rather than production hardware, since many operations can change device state or erase data.