Android-MCP and mobile-mcp
These are competitors—both provide MCP servers for mobile device automation, with the more established CursorTouch tool offering Android-specific functionality while runablehq's offering provides cross-platform mobile automation, forcing users to choose based on their platform needs and maturity requirements.
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 mobile-mcp
runablehq/mobile-mcp
A Model Context Protocol (MCP) server that provides mobile automation capabilities.
Leverages Android Debug Bridge (ADB) to interact with physical devices and emulators, parsing UI hierarchies as structured text dumps that LLMs can reason about without visual processing. Integrates directly with Claude Desktop and VS Code through MCP, enabling AI assistants to programmatically tap, swipe, and navigate mobile interfaces. Currently supports Android with iOS support planned.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work