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.
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 adb-mcp
srmorete/adb-mcp
An MCP (Model Context Protocol) server for interacting with Android devices through ADB in TypeScript.
Exposes comprehensive Android device control through stdio-based MCP tools including app installation, logcat filtering, file transfer, shell execution, and UI inspection via screenshot/XML hierarchy dumps. Designed as a Claude Desktop integration that bridges AI models with local ADB commands, supporting Android 8.0+ devices and emulators with configurable ADB paths. Provides both high-level operations (APK deployment, permission management) and low-level access (custom shell commands, activity/package manager control).
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work