brickproof-adb
Related Servers
Alternatives to brickproof-adb
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive an Android TV or Google TV box end to end through named tools — discover, pair, connect, check, install, provision, link, test, screenshot, report and a gated shell — with usage instructions embedded in the tool descriptions so the agent never improvises adb. Every command passes the same safety gate that refuses destructive actions.1Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceSet up Android TV, Google TV and Fire TV boxes over ADB on the local network: discover and pair boxes, set any launcher as the HOME app, install apps, take screenshots and run checks. No raw shell tool; the tools that change the box ask before they run.Apache 2.0
- 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.111MIT
- AlicenseBqualityCmaintenanceEnables AI agents to control Android TV/Android devices through ADB, including screen capture, remote control, app management, and more.242 npm1MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with Android devices and emulators via ADB, providing tools for screenshots, UI inspection, touch and text input, app management, and device control.4259 npm20MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to read and control a connected Android device over adb or a local root shell, with tools for screen inspection, tapping, typing, swiping, launching apps, and system commands.181MIT
TDQS
Scored across 18 tools
Most tools target a distinct action+resource, and descriptions explicitly steer selection (e.g. adb_ui_dump vs adb_screenshot, adb_tap vs adb_find_and_tap). There is deliberate overlap in package operations (adb_app, adb_install, adb_uninstall) and UI tapping (adb_tap vs adb_find_and_tap), but the guidance on when to prefer each largely resolves it.
Every tool follows the same adb_verb_noun snake_case pattern (adb_ui_dump, adb_install, adb_pull, adb_logcat). No mixed conventions or stray naming styles.
18 tools is slightly on the heavy side but each covers a genuine sub-domain: connection (devices/connect/pair/disconnect), UI interaction, package management, file transfer, shell and logs. Nothing is redundant enough to feel padded.
The surface covers the ADB lifecycle well: discovery/connection, UI automation, package management with rollback, file transfer, shell and logcat. Minor gaps exist (e.g. port forwarding, reboot, app data inspection) but they are workarounds rather than blocking omissions.