mcp -adb

This MCP server exposes a suite of ADB (Android Debug Bridge) tools that let Claude interact with connected Android devices. It includes capabilities to list devices, inspect installed packages, install or uninstall apps, push and pull files, manage permissions and app data, take screenshots, and control activities and app state on devices. Each tool accepts device targeting parameters (deviceId, useUsb, useEmulator) to direct actions to specific devices or emulators. The server is designed to be invoked via the Claude desktop integration, returning structured results that Claude can parse and use in conversations.

Available tools cover common device management tasks: get-devices returns a list of connected devices with details; install-apk and uninstall-apk manage app lifecycle; list-packages filters and reports installed applications; push/pull transfer files; screencap saves screenshots; start-activity launches app components; and several permission-related commands (grant-permission, revoke-permission, reset-permissions) help manage app permissions. There are also utilities to remove files (rm) and to manage the ADB server state (start-server, kill-server). When used together, these tools allow scripted device automation and rich interaction with Android devices from Claude.

Prerequisites:

• Node.js and npm installed on the host machine
• Android SDK Platform Tools installed and adb accessible in PATH or at a known location
• A compatible Android device or emulator connected via USB or network

Installation steps:

1. Clone the repository:

git clone [repository-url]
cd mcp-server-adb

2. Install dependencies:

npm install

3. Build the server (if a build step is required by the project):

npm run build

4. Start the server locally to verify it runs (adjust paths as needed):

node -y build/index.js /path/to/adb

5. Prepare Claude integration by referencing the server in claude_desktop_config.json (see below) and ensure adb is accessible at the provided path.

Tips and notes:

• Ensure ADB is installed and included in your system PATH, or provide the full path to the adb executable when configuring the server in Claude.
• When using flags in tools like list-packages or start-activity, you can combine multiple boolean options to filter results precisely.
• The configuration example in Claude Desktop uses command: node and points to the built index.js along with the path to adb; adjust /path/to/mcp-server-adb/build/index.js and /path/to/adb to your environment.
• If you encounter device recognition issues, check USB debugging permissions on the device, authorize a computer when prompted, and ensure USB drivers are installed on Windows if applicable.
• Some operations may require additional permissions on the device (grantPermissions), and certain operations may prompt for user confirmation on the device itself.
• For large APKs or slow connections, consider increasing timeouts in your integration layer if supported by the MCP server.