$ loading_
Control Android devices through AI for testing, debugging, and automation.
This tool claims full vision and control over Android devices via ADB and scrcpy, with no cloud credentials and no declared remote endpoints, but it has high local privileges including command execution, device control, file access, and clipboard access, so it should be used with caution. Its open-source MIT-licensed status is a positive factor, but low adoption and unknown maintenance mean users should review the source and minimize granted access.
The material explicitly states that no keys or environment variables are required, and no API tokens, account credentials, or third-party authentication are mentioned; credential exposure surface appears low.
No remote endpoints are declared, and the description focuses on controlling Android devices locally via ADB/scrcpy; based on the provided material, there is no factual indication of user data being sent to external services.
The system flags code execution, and the description includes shell, UI automation, input, and apps, indicating it invokes ADB/scrcpy locally and can trigger device commands and interactions. This is a common high-privilege MCP capability and warrants restricting connected devices and execution scope.
The description explicitly supports screenshots, files, and clipboard, and claims full vision and control over Android devices, implying access to sensitive data such as screen contents, files, and clipboard data on the device. The material does not show system permissions beyond its stated purpose, but the accessible data scope is broad.
The repository is open source and MIT-licensed, which improves auditability and is a positive risk-reducing factor; however, it comes from a third-party registry, has only 0 stars, unknown maintenance status, and no README details here, so supply-chain maturity and ongoing maintenance signals are weak.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "scrcpy-mcp" yet — see the docs or source repo.
After connecting the Android device, open my app and check whether login, home page loading, and the settings page work correctly. If any error appears, take a screenshot and summarize the result of each step.
A step-by-step test log, notes for any error screenshots, and a brief pass/fail conclusion.
Open the app's signup flow, capture screenshots from the welcome page to the submit page, and check whether buttons, titles, and helper text are consistent. Then list the issues found.
Page-by-page screenshot notes and a list of copy and UI consistency issues.
Check the current foreground app, clipboard contents, and files in a specified directory on this Android device, run common troubleshooting commands, and summarize the key diagnostic information.
A device status summary, command results, relevant file details, and suggested next troubleshooting steps.
Control Android and iOS devices for UI automation, screenshot analysis, and testing.
Control multiple iOS and Android devices for testing, screenshots, and UI actions.
Control Android devices via ADB for UI interaction and inspection.
Control Android devices with natural language for UI and system automation.
Automate Android UI interactions, snapshots, and gesture recording through MCP.
Remotely control Android devices via ADB for debugging, testing, and management.