adb-mcp and scrcpy-mcp
Both tools are MCP servers for Android device control via ADB, but one (srmorete/adb-mcp) focuses on general ADB interaction, while the other (JuanCF/scrcpy-mcp) specifically integrates scrcpy for visual control, making them **competitors** if the goal is general ADB control, but **complements** if the srmorete/adb-mcp server provides foundational ADB interactions that the scrcpy-mcp server could leverage or extend.
About adb-mcp
srmorete/adb-mcp
An MCP (Model Context Protocol) server for interacting with Android devices through ADB in TypeScript.
This tool helps AI models interact with Android devices by translating complex device operations into simple instructions. It takes an AI model's requests (like 'install app' or 'take screenshot') and executes them on a connected Android phone or emulator. This is for AI developers building or testing applications that need to automate interactions with Android devices, such as for testing, data collection, or research.
About scrcpy-mcp
JuanCF/scrcpy-mcp
MCP server for Android device control via ADB and scrcpy — gives AI agents vision and control over Android devices
Implements a **34-tool SDK** exposing screenshots (with actual image data), touch input, app lifecycle, UI element finding, shell execution, and file transfer — all over stdio transport compatible with Claude, Cursor, and VS Code Copilot. Uses scrcpy's binary protocol for 10-50x faster input latency and ~33ms screenshots when a session is active, with automatic ADB fallback for every operation. Includes Android 10+ clipboard workarounds and UI hierarchy inspection via XML dumps to enable AI agents to both see and meaningfully interact with device state.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work