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
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-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.
Exposes 54 MCP tools via an HTTP server running directly on Android, enabling AI models to interact with any app through accessibility services and UI node introspection. Uses Ktor with optional HTTPS, streamable JSON transport, and token-optimized compact screen state representation with annotated screenshots rather than verbose XML dumps. Integrates with Cloudflare Quick Tunnels and ngrok for internet-accessible remote control, plus file operations via Storage Access Framework and camera/notification management via Android system APIs.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work