adb-mcp-server
Allows control of an Android device over the network via ADB, providing tools for screen capture, UI hierarchy dump, shell commands, file push/pull, APK installation, and input simulation (tap, swipe, keyevent, text).
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
adb-mcp-server
ADB over MCP. Drive an Android device over the network from any MCP-compatible agent.
What problem this solves
You have an Android device — phone, tablet, e-reader — that you want an LLM agent to operate. The other ADB MCP servers on GitHub assume the device is plugged into the same machine the agent runs on. That doesn't work if the agent lives on a server (a droplet, a CI runner, a home-lab box) and the device is somewhere else on the network.
This server is built for that network-first case. The device is reachable at <host>:5555 over Wi-Fi, Tailscale, a VPN — anything routable. The design follows from that:
No tool-call races. All ADB calls go through a single queue, so parallel agent calls don't trample each other.
No screencap loops. Captures are rate-limited to one per 10 seconds.
Classified errors. The agent can tell "device offline" from "ADB unauthorized" from "host unreachable", and recover differently.
Path allowlists on push/install.
adb_pushandadb_installreject sources outside configured prefixes, with traversal-resistant checks.
Related MCP server: webadb-agent
How to use it
Claude Desktop / Claude Code
// e.g. ~/.config/claude/mcp.json
{
"mcpServers": {
"adb": {
"command": "npx",
"args": ["-y", "@sfaizi24/adb-mcp-server"],
"env": { "ADB_HOST": "192.168.1.42" }
}
}
}OpenClaw
# plugins.entries.acpx.config.mcpServers
adb:
command: npx
args: ["-y", "@sfaizi24/adb-mcp-server"]
env:
ADB_HOST: "100.64.0.5"Manual / dev
git clone https://github.com/sfaizi24/adb-mcp-server.git
cd adb-mcp-server
npm install
ADB_HOST=192.168.1.42 node index.jsTools
adb_status— Connection check + device info (model, Android version, SDK level).adb_shell— Run a shell command. Output truncated at 100KB.adb_screencap— Capture the screen as PNG, saved to a temp file on the host. Rate-limited to 1 per 10s.adb_ui_dump— Structured JSON dump of the UI hierarchy, with computed centerpoints for taps. Filters:clickable_only,with_text_only,include_raw_xml.adb_install— Install an APK. Reinstalls allowed; downgrades blocked. Source path allowlisted.adb_push— Push a file from host to device. Source path allowlisted.adb_pull— Pull a file from device to host. Default destination is/tmp/.adb_input— Simulate input:tap(x, y),swipe(x1, y1, x2, y2, duration_ms?),keyevent(code),text(value).
Requirements
Node 18+
adbon PATH, or setADB_BINto its absolute pathmacOS:
brew install android-platform-toolsLinux:
apt install android-tools-adb, or download the SDK platform-tools archiveWindows: download platform-tools, add the directory to PATH
A target Android device with ADB over TCP enabled (see below)
Enabling ADB over TCP on the device
One-time setup:
Connect the device to a host via USB.
On the device: enable Developer Options, then USB debugging.
Approve the host's ADB key when prompted.
On the host:
adb tcpip 5555.Unplug. The device now accepts ADB at
<device-ip>:5555.
Find the device's IP under Settings → About → Status, or in the Wi-Fi details. On Tailscale, use the Tailscale IP.
ADB over TCP usually does not survive reboot. Re-plug and run adb tcpip 5555 again to re-enable.
Configuration
Variable | Required | Default | Purpose |
| yes | — | Device hostname or IP. |
| no |
| ADB TCP port on the device. |
| no |
| Path to the |
| no |
| Comma-separated absolute prefixes that |
| no |
| Comma-separated absolute prefixes that |
Security
This server gives any connected agent shell access and APK install ability on the target device. Only run it on hosts where you trust the agents that can call its tools.
Network ADB has no authentication. Anyone with network reach to
<device>:5555can connect. Restrict via firewall, Tailscale ACL, or VPN. Do not expose port 5555 to the open internet.adb_pushandadb_installallowlist source paths (default/tmp/). The check resolves paths first (path.resolve), so../traversal does not bypass it. Symlink leaves are rejected; symlinked ancestor directories are not separately blocked — keep allowlist directories out of writable-by-untrusted-user space.
License
MIT. See LICENSE. Contributions accepted under the same terms — please run npm test before opening a PR.
Acknowledgements
Built on @modelcontextprotocol/sdk.
Related MCP Connectors
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
Melaya is a remote MCP server. It gives an assistant hands on your own Android phone and browser: it reads the screen through the accessibility tree, then taps, types and navigates inside the apps and sites you allow-list, with no per-app API. It also builds, schedules and runs agent pipelines across 6k+ connected tools. OAuth 2.1, nothing to install.
Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.
Cloud Android phones for AI agents: create a phone, read the screen, tap, type, install APKs, park.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables controlling an Android device from an MCP client via ADB, including wireless debugging discovery, UI-tree inspection, and performing taps, swipes, typing, app actions, and shell commands without relying on screen coordinates.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control a physical Android device or Docker-hosted emulator over ADB by taking screenshots and performing taps, swipes, key presses, text input, shell commands, app launches, and device info queries. It runs as a local MCP stdio server alongside a web UI and REST API for remote access.1MIT
- AlicenseCqualityBmaintenanceExposes Android device automation tools to MCP clients, letting AI agents inspect UI trees, interact with elements, launch/stop apps, run shell commands, transfer files, and manage events/tasks over adb/uiautomator2 without installing anything on the device.60MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to see and control Android devices through screenshots, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming. It connects over ADB with optional low-latency acceleration for faster input and near-instant screenshots.365 npmMIT