mobile-mcp and Android-Mobile-MCP
The two tools are ecosystem siblings: `runablehq/mobile-mcp` is a foundational Model Context Protocol server for mobile automation, while `erichung9060/Android-Mobile-MCP` appears to be a specialized implementation leveraging that protocol specifically for AI agent control of Android devices.
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.
About Android-Mobile-MCP
erichung9060/Android-Mobile-MCP
🤖 This MCP server enabling AI agents to control Android devices.
Provides granular UI automation through ADB, extracting hierarchical element trees and calculated click coordinates to enable agents to navigate complex Android interfaces programmatically. Implements MCP as a stdio-based server that integrates with Claude and other AI platforms via standard configuration, bridging on-device XML parsing with remote AI reasoning for intelligent app control and interaction sequencing.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work