Android-MCP and scrcpy-mcp
These are complements that serve different layers of Android automation: CursorTouch provides direct touch/UI interaction primitives, while scrcpy-mcp adds screen vision and remote control capabilities that can be combined for more sophisticated automation workflows.
About Android-MCP
CursorTouch/Android-MCP
MCP Server for interacting with Android Devices.
Implements an MCP server that bridges LLM agents to Android devices via ADB and the Accessibility API, enabling app navigation, UI interaction, and automated testing without computer vision models. Exposes a rich toolset including gesture controls (tap, swipe, drag), text input, view hierarchy inspection, and shell command execution—with typical action latency of 2-4 seconds. Integrates directly with Claude Desktop and any LLM/VLM, supporting Android 10+ devices and emulators.
About scrcpy-mcp
JuanCF/scrcpy-mcp
MCP server for Android device control via ADB and scrcpy — gives AI agents vision and control over Android devices
Implements a **34-tool SDK** exposing screenshots (with actual image data), touch input, app lifecycle, UI element finding, shell execution, and file transfer — all over stdio transport compatible with Claude, Cursor, and VS Code Copilot. Uses scrcpy's binary protocol for 10-50x faster input latency and ~33ms screenshots when a session is active, with automatic ADB fallback for every operation. Includes Android 10+ clipboard workarounds and UI hierarchy inspection via XML dumps to enable AI agents to both see and meaningfully interact with device state.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work