buddy-android
Related Servers
Alternatives to buddy-android
- AlicenseAqualityBmaintenanceEnables 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.182MIT
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.519MIT
- 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.392 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.392 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.392 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.392 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.392 npmMIT
TDQS
Scored across 48 tools
Despite 48 tools, boundaries are mostly clear: tap vs long_press vs swipe vs scroll vs press are distinct gestures, and confirm vs ask are explicitly contrasted (approval vs question). A few pairs require close reading of descriptions to separate—wait vs wait_for, screenshot vs browser_screenshot, open_url vs browser_open, and scroll vs swipe—but the descriptions resolve them.
All names are snake_case, but ordering conventions are mixed: verb_noun (read_screen, set_alarm, add_calendar_event), bare verbs/nouns (tap, scroll, confirm, ask), prefix groupings (browser_read, browser_open, clipboard_write), and noun-first names (device_status, calendar_events). Readable overall, but the browser_/clipboard_ prefixes invert the dominant verb_noun pattern.
48 tools is far above the 25-tool threshold where a set feels heavy, and many near-siblings (four browser_* tools, three wait/install tools, several gesture tools) burden selection. The breadth of Android automation justifies many of them individually, but the surface is too large to scan comfortably.
Coverage is broad: screen reading, gestures, text entry, app launching, background browsing, clipboard, alarms/timers, calendar read+add, notifications, media, location, photo, sharing, APK install/update, and scheduling. Minor gaps remain—no contacts access, no general file read/write from the work folder, no shell/command tool despite referencing Buddy's Linux, and no settings toggles beyond press-driven navigation.