phone-use
Related Servers
Alternatives to phone-use
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables coding agents to control a locally connected Android phone or emulator over ADB through MCP tools for device setup, UI inspection, taps, swipes, Unicode text input, app launching, and bounded batch actions, plus a live screen sidebar with clipboard capture.26MIT
- AlicenseNot gradedqualityDmaintenanceEnables coding agents to observe and operate Android devices through ADB and uiautomator2, supporting screenshot capture, UI hierarchy access, and actions like tap, swipe, and text input.2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables Android device control over ADB through MCP tools that mirror CLI subcommands, including taps, swipes, text input, app launch/stop, screenshots, UI inspection, and running action sequences. Coordinates from screenshots are converted to screen coordinates automatically.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control an Android phone by reading the screen, taking screenshots, tapping, typing, swiping, opening apps, and running multi-step tasks. It also supports on-device Android app testing and optional adb commands.1,085 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control Android phones via MCP and HTTP. Supports screen capture, taps, swipes, text input, and app management.7AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to remotely control a real Android phone over MCP with no ADB, root, or emulator, by connecting a broker server to a sideloaded APK. Exposes tools to list devices, capture screenshots, read the UI tree, open links and deep links, and perform taps, swipes, typing, and global navigation actions.1MIT
TDQS
Scored across 13 tools
Most tools have distinct purposes, but there is some overlap: phone_tap vs phone_tap_element, phone_observe vs phone_find_elements, and phone_swipe vs phone_scroll. The descriptions clarify the differences (coordinate-based vs snapshot-based, raw swipe vs observe-verify), so an agent can distinguish them with care.
All 13 tools use a consistent phone_ prefix followed by a snake_case verb or noun phrase. The pattern is predictable and readable throughout.
13 tools is well within the ideal 3-15 range and each tool covers a distinct capability needed for ADB-based phone automation. No tool feels redundant or out of scope.
The surface covers device discovery, status, UI observation, interaction (tap, swipe, scroll, keys, text), app listing/launching, and screenshots. Minor gaps remain, such as app install/uninstall, file transfer, shell commands, and explicit field clearing, but core phone-control workflows are covered.