NexusAndroid
Related Servers
Alternatives to NexusAndroid
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.154 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.154 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control Android devices through ADB and scrcpy, including screenshots, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, audio/video streaming, and clipboard access.154 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.154 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.154 npmMIT
TDQS
Scored across 11 tools
Each tool targets a distinct primary purpose: diagnostics (checkup), visual state (look), gesture execution (act), app launching (launch), SMS/RCS reading (messages), reply drafting (draft), notifications, file transfer, read-only info, settings toggles, and connection status. Minor overlaps such as checkup vs phone for status or messages vs notifications for phone data are clarified by descriptions, so an agent can reliably choose the right tool.
All names are single lowercase words with no mixed camelCase or snake_case, giving a consistent surface format. However, they mix verbs (look, act, launch) and nouns (messages, files, settings, phone), so there is no single action-oriented pattern like verb_noun throughout.
11 tools is well within the sweet spot for an Android phone control server. Each tool covers a distinct area of functionality and earns its place, with no obvious redundancy or bloat.
The surface covers core workflows: diagnostics, screen reading, gestures, app launching, SMS/RCS, reply drafting, notifications, files, location/calls/contacts/calendar, settings, and connection state. Direct send-message, call, media, and app-management operations are absent, but the general act tool provides a UI-automation workaround, leaving minor gaps rather than dead ends.