phone-mcp and android-remote-control-mcp
Tool A appears to be a plugin for the MCP (Mobile Control Protocol) that uses ADB for Android phone control, while Tool B is an MCP server optimized for Android, suggesting they could be **complements** where Tool A acts as a client or specific control layer that interacts with Tool B running on the phone as the server.
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
This tool helps automate tasks on your Android phone by letting you control it through text commands, often via an AI assistant. You can give it instructions like 'call Hao' or 'open netease music', and it will perform the actions on your phone. It's designed for anyone who wants to automate repetitive phone interactions or integrate phone control into larger automated workflows.
About android-remote-control-mcp
danielealbano/android-remote-control-mcp
An MCP Server for Android running on the phone, optmized for token usage, supports also files downloads and cloudflare (free) and ngrok automated tunnelling.
This project allows an AI model to fully control an Android phone remotely, directly from the device. It takes AI commands as input and executes actions like tapping, typing, swiping, managing files, or opening apps on the Android device, returning screen state and confirmation. It's designed for researchers or educators developing AI agents that interact with mobile applications.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work