$ loading_
Control Android devices over ADB for debugging, inspection, and automation tasks.
This MCP tool mainly controls an Android device over ADB across the network, with no cloud credentials required and no stated third-party data exfiltration. Its main risk surface is device control, command execution, and access to device data, so the overall posture is caution rather than high risk.
The material explicitly states that no keys or environment variables are required, and no API tokens, account credentials, or third-party authentication needs are shown, so credential exposure appears limited.
The description shows it communicates with an Android device over networked ADB, meaning commands, screenshots, files, and UI data may transit between the host and the target device; however, no unrelated third-party endpoint or cloud service is indicated.
The system flags executes-code, and the description explicitly supports shell commands, indicating it can invoke local ADB-related processes and execute commands on the device. This is a core capability of this tool class and warrants caution around which devices and actions are allowed.
The material lists screen capture, UI inspection, and file operations, indicating access to screen content, UI structure, and file data on the connected Android device, plus input simulation that can alter device state; no host permissions beyond the stated function are shown.
The project is open source and auditable under the MIT license, which materially lowers supply-chain risk; however, it comes from a third-party registry, has 0 stars, and an unknown maintenance status, so trust remains limited and source/dependency review is advisable before broader use.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "adb-mcp-server" yet — see the docs or source repo.
Connect to an Android device on the local network, run adb shell commands to collect logs, inspect the current foreground Activity, and capture the current screen to help diagnose a white screen issue after app launch.
Returns the connection status, key logs, foreground UI details, screenshot result, and initial troubleshooting suggestions.
On a connected Android device, simulate taps, enter text, launch a target app, then take a screenshot to verify success and export the image to a local directory.
Completes a sequence of automated inputs and app actions, then outputs execution status, screenshot files, and retry or failure details.
List files in a specified directory on the Android device, pull the latest log file locally, and fetch the current UI hierarchy so I can analyze screen elements and resource files.
Returns directory contents, downloaded file paths, and a structured UI inspection result for the current screen.
Remotely control Android devices via ADB for debugging, testing, and management.
Control Android devices via ADB for UI interaction and inspection.
Control Android devices via ADB for automation, testing, and debugging tasks.
Automate Android devices via ADB for testing, control, and task execution.
Control Android devices via ADB for input, screenshots, UI analysis, and app management.
Control Android devices through AI for testing, debugging, and automation.