Android UI Assist MCP Server
Related Servers
Alternatives to Android UI Assist MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables 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.4260 npm18MIT
- AlicenseAqualityCmaintenanceEnables AI agents to control, inspect, and automate Android devices, Waydroid containers, and AVD emulators over ADB. Provides tools for screenshots, UI-hierarchy text-based tapping, gestures, key presses, text input, app management, and raw shell commands.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control Android devices via ADB, providing tools for screen capture, tap/swipe/input, app management, and diagnostics. Works locally over USB or WiFi and integrates with MCP clients like Claude and Cursor.1MIT
- FlicenseBqualityCmaintenanceEnables AI assistants to observe, reason about, and control connected Android devices via ADB, providing tools for screenshots, UI hierarchy parsing, semantic element clicking, gestures, text input, and app lifecycle management.13-
- FlicenseAqualityDmaintenanceEnables AI agents to interact with Android devices through UI manipulation, screen capture, touch gestures, text input, and app management via ADB. Provides comprehensive mobile automation capabilities including element detection, navigation, and application control for Android device testing and interaction.94-
- AlicenseBqualityBmaintenanceEnables AI agents to control Android TV/Android devices through ADB, including screen capture, remote control, app management, and more.243 npmMIT
TDQS
Scored across 2 tools
The two tools have completely distinct purposes with no overlap: one lists devices, the other captures screenshots. An agent can easily differentiate between them based on their clear, specific functions.
Both tools follow a consistent verb_noun pattern (list_android_devices, take_android_screenshot) with the same prefix 'android_' for domain specificity. The naming is perfectly uniform and predictable.
With only two tools, the server feels under-scoped for an 'Android UI Assist' purpose, which typically implies broader UI interaction capabilities like clicking, typing, or inspecting elements. The count is too low for the apparent domain.
For an Android UI assistance server, there are significant gaps: no tools for interacting with UI elements (e.g., tap, input text), navigating apps, or retrieving UI hierarchies. The current tools only cover device listing and screenshot capture, leaving core UI automation workflows incomplete.