phone-mcp and Android-Mobile-MCP
Given that both tools are "phone control plugins for MCP" or "MCP servers enabling AI agents to control Android devices," they appear to be competitors, offering different implementations or feature sets for achieving similar Android device control through the MCP framework.
About phone-mcp
hao-cyber/phone-mcp
A phone control plugin for MCP that allows you to control your Android phone through ADB commands to connect any human
Implements comprehensive Android device control through ADB with native MCP server integration, exposing 20+ tool categories spanning communications (calls, SMS), media capture, app management, and UI automation via coordinate-based and element-detection interactions. Designed as a drop-in plugin for AI assistants (Claude, Cursor, Cline) with stdio transport, enabling autonomous phone workflows like weather-triggered music selection or conditional messaging without user confirmation.
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