$ loading_
Automate Android devices via ADB for testing, control, and task execution.
This tool claims to provide Android device automation and control via ADB, which inherently gives it a high-privilege local command and connected-device access surface. The materials show no required secrets or remote egress, but the project comes from a third-party registry with very low adoption and unclear maintenance, so it should be used with caution overall.
The materials explicitly state that no keys or environment variables are required, and there is no indication of API tokens, account passwords, or cloud credentials being requested, so credential exposure appears low.
The declared remote endpoints are none, and the description only mentions interacting with Android devices via ADB; there is no evidence of sending data to external services or unknown hosts.
The system checks confirm executes-code, and its core functionality depends on ADB for device control, which typically means invoking local adb processes and running device-management commands. This is a normal high-privilege capability for such tools and warrants limiting accessible devices and command scope.
The description mentions testing, automation, and device control, which reasonably implies access to device state and UI information and may include common ADB actions such as install, input, screenshots, or file transfer. The materials do not show fine-grained scope limits, so it should be treated as having broad access to connected Android devices, though there is no evidence of permissions beyond its stated purpose.
A positive factor is that an open-source repository exists, enabling source review; however, it comes from a third-party registry, has no declared license, only 0 stars, and an unknown maintenance status, so evidence of trust and maturity is weak. It is better suited for isolated evaluation after reviewing source and dependencies.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "android-mcp-server" yet — see the docs or source repo.
Connect to an Android device with ADB enabled, launch my app com.example.app, open the login page, enter the test account, submit the form, and record whether each step succeeds. If any step fails, return the failed step and a device screenshot.
Returns test execution results, failed-step details, and relevant screenshots or status logs.
Use ADB to control an Android device and complete this flow: unlock the screen, open Settings, enter Developer Options, enable Show taps, and return to the home screen when finished.
Provides execution status for each step and confirms whether the setting was enabled successfully.
Check the current Android device connection, retrieve the device model, OS version, battery information, and foreground app, then output a structured summary suitable for troubleshooting.
Returns a structured device status report for debugging, test investigation, and issue reproduction.
Control Android devices via ADB for UI interaction and inspection.
Control Android and iOS devices for UI automation, screenshot analysis, and testing.
Automate Android UI interactions, snapshots, and gesture recording through MCP.
Automate iOS and Android app interactions across simulators, emulators, and devices.
Control multiple iOS and Android devices for testing, screenshots, and UI actions.
Control Android devices through AI for testing, debugging, and automation.