DroidPath
Related Servers
Alternatives to DroidPath
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceA lightweight bridge enabling AI agents to perform real-world tasks on Android devices such as app navigation, UI interaction, and automated QA testing without requiring computer-vision pipelines or preprogrammed scripts.14932MIT
- AlicenseBqualityBmaintenanceEnables AI agents to drive a rooted Android phone using OS-reported semantics rather than screenshots or OCR: it reads a single hierarchy dump into typed, addressable controls and injects taps, swipes, and key events through a resident native daemon in tens of milliseconds. It also probes and remembers the effect of controls the OS leaves unlabeled, so subsequent screen descriptions carry learned annotations instead of guesses.575MIT
- AlicenseAqualityBmaintenanceEnables an LLM agent to control a real Android phone by choosing runtime-discovered targets from live device state, with safety gating and approval for mutating commands.3MIT
- AlicenseBqualityBmaintenanceAn embeddable Android automation runtime with an on-device MCP server and an autonomous agent (DeepSeek plans, TypeSafe Jev picks each tap, code verifies). Workflows are flat JSON that LLMs can write; execution goes through accessibility + system APIs.783MIT
- AlicenseAqualityBmaintenanceRuntime access for AI coding agents to observe and control Android and iOS apps.520 npm9MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to automate real desktop applications across Windows, Linux, and macOS using incremental screen perception, accessibility trees, OCR, and window management, dramatically reducing token usage compared to screenshot-per-step approaches.36 PyPI4MIT
TDQS
Scored across 9 tools
The nine tools cover distinct layers: symbolic A* routing (navigate_to_node), dynamic discovery with optional routing (explore_and_click), raw element lookup (get_ui_tree), and a manual low-level tap (tap_element). There is some residual overlap since navigate_to_node, explore_and_click, and tap_element can all end in a tap, but the descriptions clearly delineate graph-routing vs. discovery vs. direct targeting.
All tools share the android_ prefix and snake_case, with most following a verb_noun shape (android_tap_element, android_swipe, android_list_devices). Minor deviations exist in noun-only forms like android_graph_stats and android_keyevent, but the convention remains predictable.
Nine tools is a well-scoped surface for an Android automation server, with each tool earning its place across graph routing, discovery, introspection, and primitive input actions. No redundant or filler tools are present.
Core interaction primitives (tap, swipe, type, keyevent, navigate, explore, UI tree, device listing) are covered, but notable gaps remain for an Android automation domain: no screenshot or visual capture, no app launch/package management, and no explicit wait-for-element or long-press/lifecycle operations.