android

This MCP server provides a bridge between Claude and an Android device over ADB. It exposes a set of tools that let you enumerate devices, inspect installed packages, push and pull files, install or uninstall APKs, manage app data and permissions, take screenshots, and perform various utility actions directly from the MCP protocol. The tools are designed to be invoked via MCP commands with structured parameters, enabling automated workflows and remote device control. Typical use cases include automating app testing, gathering device information, and performing scripted APK deployment or cleanup on connected devices.

Prerequisites:

• Node.js and npm installed on your machine
• ADB (Android Platform Tools) installed and accessible in your PATH
• A device connected with USB debugging enabled, or an emulator accessible via ADB

Install and build the server:

1. Clone the repository git clone https://github.com/jiantao88/android-mcp-server.git cd android-mcp-server
2. Install dependencies npm install
3. Build the project (produces build/index.js) npm run build

Usage example (local):

• Run the MCP server pointing to your ADB executable node build/index.js /path/to/adb

Configure Claude Desktop (example):

• In claude_desktop_config.json, add an MCP server entry like: { "mcpServers": { "adb": { "command": "node", "args": ["-y", "/path/to/android-mcp-server/build/index.js", "/path/to/adb"] } } }

Notes:

• Ensure the paths are absolute and the adb executable is accessible.
• If you change the project path, update the arguments accordingly.

Tips and common issues:

• Ensure ADB is in your system PATH and devices are authorized (ADB adb devices should list devices).
• The server depends on a built index.js; always run npm run build after pulling updates.
• Use absolute paths in your MCP configuration to avoid runtime path resolution issues.
• If an operation requires device permission changes (grant-permission, reset-permissions), ensure the target app is installed on the device.
• For screen captures, the remotePath should be a valid path on the device (e.g., /sdcard/screenshot.png).
• When listing packages, you can combine flags like showSystem, showThirdParty, showPath, etc., to tailor results to your needs.
• If you run into ADB connection drops, verify USB debugging authorization on the device and retry the command.