Android Phone MCP
Related Servers
Alternatives to Android Phone MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to see and control Android devices through ADB and a fast device-control protocol, including screenshots, touch input, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming.392 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables controlling an Android device from an MCP client via ADB, including wireless debugging discovery, UI-tree inspection, and performing taps, swipes, typing, app actions, and shell commands without relying on screen coordinates.8 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to see and control Android devices through screenshots, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming. It connects over ADB with optional low-latency acceleration for faster input and near-instant screenshots.392 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control Android devices via ADB, providing tools for screen capture, tap/swipe/input, app management, and diagnostics. Works locally over USB or WiFi and integrates with MCP clients like Claude and Cursor.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to operate adb-connected devices through natural language by exposing shell execution, file management, screenshots, notifications, and system information tools over a local MCP endpoint. It supports wireless device access from a phone-hosted Termux environment with automatic reconnection and dangerous-command confirmation.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control a physical Android device or Docker-hosted emulator over ADB by taking screenshots and performing taps, swipes, key presses, text input, shell commands, app launches, and device info queries. It runs as a local MCP stdio server alongside a web UI and REST API for remote access.1MIT
TDQS
Scored across 15 tools
Each tool maps to a distinct step in the phone-control lifecycle, and descriptions explicitly differentiate easily-confused pairs (discover vs devices, pair vs connect, tap vs tap_element). The only real blur is android_screen vs android_screenshot, since android_screen can fall back to returning a PNG, but the descriptions call this out clearly.
All tools share the android_ prefix and use snake_case, which makes the set highly predictable. However, the verbs are mixed: some are actions (tap, swipe, connect, pair) while others are bare nouns (info, screenshot, screen, apps), so the verb_noun pattern is not fully uniform.
15 tools is well within a healthy range and each one earns its place: discovery, pairing, connection, selection, inspection, input and app launching are all separate concerns. There is no obvious padding or redundant capability.
The surface covers the full connection lifecycle plus core interaction (screen read, screenshot, tap, tap_element, swipe, type, key, apps, launch). Minor gaps remain: no disconnect/unpair, no long-press or drag gestures, no shell/notification/file operations, and typing is limited to ASCII.