nexus-android
Related Servers
Alternatives to nexus-android
No user-submitted related servers found.
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.19MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to visually perceive and directly control Android devices via ADB and screen-control tooling, including screenshots, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming.162 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents vision and control over Android devices through ADB and scrcpy, enabling screenshots, taps, swipes, typing, app launching, UI element inspection, file transfer, and shell commands. Input and screen capture stay fast via scrcpy's binary control protocol, with an ADB fallback when no session is active.162 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control Android devices through ADB and scrcpy, supporting screenshots, input, app management, UI automation, shell/file access, and audio/video streaming.162 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control Android devices through ADB and screen mirroring, supporting screen capture, touch input, app management, UI element finding, file transfer, shell commands, clipboard access, and audio/video streaming.162 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control Android devices through ADB and scrcpy, supporting screen capture, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming.162 npmMIT
TDQS
Scored across 11 tools
Most tools target distinct resources: look (screen), files (storage), info (read-only data), settings (toggles), checkup (diagnostics), messages/draft/notifications (comms). Minor overlap exists where act can perform open_url or gestures that launch/draft also accomplish, and phone's foreground-app readout nudges into look's territory, but descriptions make boundaries clear.
All 11 names are single lowercase words with no separators, giving a very uniform format (look, files, info, settings, phone, checkup, act, launch, messages, draft, notifications). There is no verb_noun convention and verbs (act, launch) sit beside nouns (files, settings), but the style itself is consistent and readable.
11 tools is squarely in the well-scoped 3-15 range for a phone-control agent. Each tool maps to a coherent capability area (screen, input, files, info, settings, comms) without redundancy or padding.
Coverage is strong across screen reading, input, files, settings, diagnostics, and messaging lifecycle, with deliberate safety omissions (no delete, draft+act instead of direct send). Gaps remain around initiating calls or installing/removing apps, but core agent workflows are workable.