Android-MCP and adb-mcp
These are complements that serve different interaction patterns—CursorTouch provides direct touch/UI automation capabilities while adb-mcp exposes lower-level ADB command execution, allowing them to be used together for comprehensive Android device control (UI-level actions plus system-level commands).
About Android-MCP
CursorTouch/Android-MCP
MCP Server for interacting with Android Devices.
This tool helps quality assurance engineers, mobile app testers, and anyone needing to automate Android device interactions. It takes natural language commands and translates them into actions like app navigation, UI taps, text input, and gesture controls on Android 10+ devices. The result is automated testing, task execution, and UI interaction without manual effort or complex coding.
About adb-mcp
srmorete/adb-mcp
An MCP (Model Context Protocol) server for interacting with Android devices through ADB in TypeScript.
This tool helps AI models interact with Android devices by translating complex device operations into simple instructions. It takes an AI model's requests (like 'install app' or 'take screenshot') and executes them on a connected Android phone or emulator. This is for AI developers building or testing applications that need to automate interactions with Android devices, such as for testing, data collection, or research.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work