SuperAPI AI Directory

android-mcp-server

Android device control via ADB: screenshots, UI tree inspection, touch automation, logcat and compound actions like tap-and-wait.

Open website

About this tool

Purpose: Use ADB to let AI assistants "see, operate, and debug" Android apps, suitable for MCP-capable clients such as Claude Code, and usable for defect reproduction and documentation, verification of interface flows such as login, smoke testing after APK installation, and element interaction automation.

Main capabilities: Provides 25 tools, covering device management (list devices, start emulator, get device information), screenshots (Sharp-based compression, longest side up to 1280px), UI tree inspection (read element hierarchy and its bounds, text, resource-id, state), touch automation (tap, swipe, scroll, type text, press hardware keys), element location (find and click by resource-id, text, or content-desc), app lifecycle (install APK, launch app, view current Activity), logcat integration (filter by package name, log level, or timestamp), and composite actions (such as tap_and_wait combining tap, wait for stability, and read UI tree into a single round trip). There is also persistent ADB shell, device information caching, and multi-device targeting by ID support.

Usage: Requires installing Android SDK and platform-tools (ADB) and emulator first, and preparing a running emulator or connected device. The server automatically discovers the SDK at ~/Library/Android/sdk on macOS or via ANDROID_HOME; if the SDK is elsewhere, set ANDROID_HOME in the MCP configuration. The server can be registered globally, or restricted to the current project with --scope project; it can also be written into the Claude Desktop configuration, VS Code's .vscode/settings.json, Cursor's ~/.cursor/mcp.json, Windsurf's ~/.codeium/windsurf/mcp_config.json, or the project's .mcp.json. The server communicates via stdio according to the Model Context Protocol; all device interaction goes through ADB, and the app requires no modifications.

Limitations: The material does not provide specific commands and code examples; the prerequisites for use are having Android SDK, ADB, and an available emulator or physical device; screenshots are compressed, with a maximum longest side of 1280px; the repository is released under the MIT license.