Provides Android Debug Bridge (ADB) functionality for automating Android devices, including device management, screen operations (screenshots, touch input), app management (install/uninstall, start/stop), file operations, and shell command execution.
Enables file operations on Android devices including pushing files to device, pulling files from device, listing files and directories, creating directories, and deleting files.
Allows execution of shell commands on Android devices to get system information, battery information, and logcat output, with basic security measures to block dangerous commands.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ADB MCP Server take a screenshot of my device"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server that provides Android Debug Bridge (ADB) functionality for automating Android devices.
List connected devices
Get device information
Set default device for operations
Check device connection status
Take screenshots
Click at coordinates
Swipe gestures
Input text
Press keys
Install/uninstall apps
Start/stop apps
List installed apps
Get app information
Push files to device
Pull files from device
List files and directories
Create directories
Delete files
Execute shell commands
Get system information
Get battery information
Get logcat output
Related MCP server: Android ADB MCP Server
Clone the repository
Install dependencies:
npm installBuild the project:
npm run buildAndroid Debug Bridge (adb) must be installed and available in PATH
Android device connected via USB with USB debugging enabled
Device must be authorized for debugging
npm startadb_list_devices - List all connected devices
adb_get_device_info - Get device information
adb_set_default_device - Set default device
adb_screenshot - Take screenshot
adb_click - Click at coordinates
adb_swipe - Swipe gesture
adb_input_text - Input text
adb_press_key - Press key
adb_install_app - Install APK
adb_uninstall_app - Uninstall app
adb_start_app - Start app
adb_stop_app - Stop app
adb_list_apps - List installed apps
adb_push_file - Push file to device
adb_pull_file - Pull file from device
adb_list_files - List files in directory
adb_shell - Execute shell command
adb_get_system_info - Get system information
adb_get_battery_info - Get battery information
adb_get_logcat - Get logcat output
The server includes basic security measures:
Dangerous shell commands are blocked
File path validation
Device connection verification
Input sanitization
npm run buildnpm run devnpm run lint "mcpServers": {
"adb-mcp": {
"type": "stdio",
"command": "node",
"args": [
"/adb-mcp/dist/index.js"
],
"env": {
"ADB_DOWNLOAD_PATH": "/adb-mcp",
"MCP_READ_PATH": "/adb-mcp"
}
}
}MIT
Click at specific coordinates on the device screen
Inputs: x (required), y (required), deviceId.
Get battery information from the device
Inputs: deviceId.
Get detailed information about a specific device
Inputs: deviceId.
Get logcat output from the device
Inputs: lines, tag, deviceId.
Get system information from the device
Inputs: deviceId.
Input text on the device
Inputs: text (required), deviceId.
Install an APK file on the device
Inputs: apkPath (required), deviceId.
List installed apps on the device
Inputs: deviceId.
List all connected Android devices
Inputs: no named parameters.
List files in a directory on the device
Inputs: remotePath (required), deviceId.
Press a key on the device
Inputs: keyCode (required), deviceId.
Pull a file from device to local system
Inputs: remotePath (required), localPath, deviceId.
Push a file from local system to device
Inputs: localPath (required), remotePath (required), deviceId.
Take a screenshot of the device screen
Inputs: deviceId, format.
Set the default device for subsequent operations
Inputs: deviceId (required).
Execute a shell command on the device
Inputs: command (required), deviceId.
Start an app on the device
Inputs: packageName (required), activityName, deviceId.
Stop an app on the device
Inputs: packageName (required), deviceId.
Swipe from one point to another on the device screen
Inputs: x1 (required), y1 (required), x2 (required), y2 (required), +2 more.
Uninstall an app from the device
Inputs: packageName (required), deviceId.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 20 tools
Every tool has a clearly distinct purpose with no ambiguity - each targets a specific Android Debug Bridge operation like clicking, getting info, installing apps, or file management. The descriptions clearly differentiate actions like adb_click vs adb_swipe, adb_install_app vs adb_uninstall_app, and adb_pull_file vs adb_push_file.
All tools follow a perfect 'adb_verb_noun' pattern consistently throughout the entire set. The naming convention is uniform with clear action-object relationships, making it easy to understand what each tool does at a glance.
20 tools is slightly high but reasonable for comprehensive Android device management. The count covers essential ADB operations without obvious bloat, though some related operations like app clearing or system property setting could potentially be added or consolidated.
The toolset provides complete coverage for Android device management through ADB, including device listing/selection, app lifecycle management (install/start/stop/uninstall), file operations, input simulation, system information retrieval, and debugging capabilities. No significant gaps exist for core ADB workflows.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
A Model Context Protocol server for Wix AI tools
Mozark's MCP server for AI-powered app testing: device access, test automation, and QA insights.