MCP SERVERInstall a build on a connected Android device, read its UI hierarchy, pull the logs and run shell — all from the session you are debugging in.
No longer maintained. The GitHub repository for this server is archived — no fixes or security updates are expected.
LABSCO SUMMARY
A build can be pushed to a device and its crash read back in the same exchange, with logcat narrowed by filter instead of scrolled through. The two ways of seeing the screen are deliberately different: inspect_ui returns XML an agent can act on, while dump_image is a picture for a person, so asking for the wrong one is the difference between automating a tap and describing one.
An ADB wrapper of ten tools: device listing, shell, Activity Manager and Package Manager subcommands, APK install, file transfer both ways, logcat, screenshots and a UI hierarchy dump.
At least one Android device or emulator connected, and npx on your PATH. Calls take a device identifier when more than one is attached. No account, no key.
One command — npx -y adb-mcp
USE CASES
List what is attached to get the device identifier the other calls take, install the APK from a local path, and start the activity through the Activity Manager rather than tapping the launcher.
Logcat filtered by tag or expression and capped by line count returns the part of the log that concerns the crash, instead of the scroll-back that surrounds it. Shell covers whatever the filter cannot express.
The UI hierarchy comes back as XML that can be parsed for the element and its bounds, which is what makes an automated tap possible. The screenshot is the human-readable counterpart and is labelled for viewing rather than parsing.
Pull returns the file as base64 so a database, a log or a config can be read directly in the session; push takes base64 the same way, which is how test fixtures get onto the device.
Package Manager subcommands list the installed packages and the permissions they hold, and grant or revoke them — which is the fastest way to test how an app behaves when a permission is denied.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
adb_activity_managerExecutes Activity Manager (am) commands on a connected Android device. Supports starting activities, broadcasting intents, force-stopping packages, and other 'am' subcommands. Specify the subcommand (e.g. 'start', 'broadcast', 'force-stop') and arguments as you would in adb shell am. Example: amCommand='start', amArgs='-a android.intent.action.VIEW -d http://www.example.com'
adb_devicesLists all connected Android devices and emulators with their status and details. Use this tool to identify available devices for interaction, verify device connections, and obtain device identifiers needed for other ADB commands. Returns a table of device IDs with connection states (device, offline, unauthorized, etc.). Useful before running any device-specific commands to ensure the target device is connected.
adb_installInstalls an Android application (APK) on a connected device or emulator. Use this for deploying applications, testing new builds, or updating existing apps. Provide the local path to the APK file for installation. Automatically handles the installation process, including replacing existing versions. Specify a device ID when working with multiple connected devices.
adb_logcatRetrieves Android system and application logs from a connected device. Ideal for debugging app behavior, monitoring system events, and identifying errors. Supports filtering by log tags or expressions to narrow down relevant information. Results can be limited to a specific number of lines, making it useful for both brief checks and detailed analysis. Use when troubleshooting crashes, unexpected behavior, or performance issues.
adb_package_managerExecutes Package Manager (pm) commands on a connected Android device. Supports listing packages, installing/uninstalling apps, managing permissions, and other 'pm' subcommands. Common commands include: 'list packages', 'install', 'uninstall', 'grant', 'revoke', 'clear', 'enable', 'disable'. Example: pmCommand='list', pmArgs='packages -3' (lists third-party packages) or pmCommand='grant', pmArgs='com.example.app android.permission.CAMERA'
adb_pullTransfers a file from a connected Android device to the server. Use this to retrieve app data files, logs, configurations, or any accessible file from the device. The file content can be returned as base64-encoded data or as a success message. Requires the full path to the file on the device. Useful for data extraction, log collection, and backing up device files.
adb_pushTransfers a file from the server to a connected Android device. Useful for uploading test data, configuration files, media content, or any file needed on the device. The file must be provided as base64-encoded content. Requires specifying the full destination path on the device where the file should be placed. Use this when setting up test environments, restoring backups, or modifying device files.
adb_shellExecutes a shell command on a connected Android device or emulator. Use this for running Android system commands, managing files and permissions, controlling device settings, or interacting with Android components. Supports all standard shell commands available on Android (ls, pm, am, settings, etc.). Specify a device ID to target a specific device when multiple devices are connected.
dump_imageCaptures the current screen of a connected Android device. FOR HUMAN VIEWING ONLY: This tool provides a visual image that cannot be easily processed programmatically. The screenshot shows exactly what appears on the device screen at the moment of capture. The default behavior returns a success message. Use asBase64=true to get the image as base64-encoded data. No additional parameters required beyond an optional device ID. Use when you need to visually verify UI elements for human inspection only. NOTE: For programmatic analysis or to identify UI elements, use inspect-ui instead.
inspect_uiCaptures the complete UI hierarchy of the current screen as an XML document. This provides structured XML data that can be parsed to identify UI elements and their properties. Essential for UI automation, determining current app state, and identifying interactive elements. Returns the UI structure including all elements, their IDs, text values, bounds, and clickable states. This is significantly more useful than screenshots for AI processing and automation tasks.
BEFORE YOU INSTALL
10 tools when we connected.
CONTEXT COST
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"adb-mcp": {
"command": "npx",
"args": [
"-y",
"adb-mcp"
]
}
}
}npx -y adb-mcpMCP servers
jiantao88
github-hewei
Neverlow512
fullread