Android-MCP and uiautomator2-mcp-server
These are complements that use different automation frameworks—one leverages the native Android UIAutomator while the other uses UIAutomator2—allowing users to choose based on their device compatibility and testing requirements, but they cannot be used together in the same MCP server instance.
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 uiautomator2-mcp-server
tanbro/uiautomator2-mcp-server
A MCP (Model Context Protocol) server that provides tools for controlling and interacting with Android devices using uiautomator2.
Exposes 70+ tools for device automation (screenshots, gestures, app management, text input) via MCP protocol, with XPath-based UI element filtering to reduce token usage and tool selection controls to minimize AI hallucinations. Implements a stdio/HTTP dual-transport architecture that bridges AI assistants with Android devices through uiautomator2 and ADB, enabling conversational automation without coding. Integrates with MCP-compatible clients (Claude Desktop, Cursor) for natural language device control and includes a built-in AI-driven testing framework for UI validation.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work