buddy-android
Related Servers
Alternatives to buddy-android
- AlicenseAqualityAmaintenanceEnables AI agents to see and drive a real Android phone over plain ADB: screenshots and numbered UI trees, gestures, typing with accents and emoji, SMS/RCS reading and prepared replies, notifications, files, and settings, with no root and no app installed on the phone. Safeguards mask security codes and require explicit confirmation before sending, paying, deleting or confirming anything.183,537 PyPI2MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceLets AI agents see and use a real Android phone over Wi-Fi: read the screen, find elements by text or ID, tap, type, swipe, take screenshots and read notifications, without ADB or root.312MIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents vision and control over Android devices via ADB and scrcpy, enabling screen capture, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, audio/video streaming, and clipboard access.151 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to see and control Android devices by capturing screenshots as images, tapping, swiping, typing, launching apps, inspecting UI elements, transferring files, streaming audio/video, and running shell commands. Uses scrcpy's binary control protocol for fast input and near-instant screenshots, with ADB fallback for interaction tools.151 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control Android devices, with fast input, screenshots, UI element discovery, app and file management, shell access, and audio/video streaming or recording.151 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control Android devices via ADB and scrcpy, supporting screenshots, taps, swipes, typing, app and UI automation, file transfer, shell commands, clipboard, and audio/video streaming.151 npmMIT
- AlicenseNot gradedqualityBmaintenanceGives AI agents vision and control over Android devices, with tools for screenshots, touch input, app and UI automation, shell access, file transfer, clipboard, and audio/video streaming.151 npmMIT
TDQS
Scored across 28 tools
Most tools are clearly scoped: phone UI actions, background-browser actions, app launching, and user interaction are distinct. The main ambiguity is between parallel phone and browser tools (tap vs browser_click, type_text vs browser_type, scroll vs browser_scroll, screenshot vs browser_screenshot), though descriptions clarify which surface each acts on.
The set uses snake_case throughout and a predictable browser_* prefix for background-browser operations. There are minor deviations such as noun-like names (screenshot, browser_tabs, browser_screenshot) among mostly verb-based names, but the pattern remains readable.
At 28 tools this is heavy, but the domain is broad: phone screen automation, background browser control, app launching, approvals, notifications, and installs. Many tools earn their place, yet the parallel phone/browser surfaces suggest some consolidation could reduce surface area.
The surface covers core Android interaction, browser control, app launching, user confirmation, and install/update flows well. Some gaps remain, such as clipboard access, richer notification listing/management, and app uninstall/force-stop operations, but agents can work around most of these.