F
licenseNot graded
qualityC
maintenanceEnables AI-driven mobile test automation through planning, generation, and self-healing agents for Android and iOS, exposed as callable MCP tools.
9
-
mobile-mcp-allinone
by xue-ding-e
Related Servers
Alternatives to mobile-mcp-allinone
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceMobile automation suite of tools including an MCP and libraries for test authoring & execution. Android first, iOS support coming.383 npm80Apache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides Android UI automation tools via MCP, enabling device interaction, UI snapshot, and gesture recording.-
- AlicenseNot gradedqualityCmaintenanceEnables AI-driven phone management for Android and iOS devices, including flashing, unlocking, and automation via MCP.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for cross-platform mobile automation (iOS/Android) using accessibility trees and screenshots, enabling agents to interact with apps on simulators, emulators, and physical devices.7Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides Appium mobile automation capabilities to Claude and other MCP-compatible clients, enabling cross-platform iOS and Android automation, element interaction, and session management.416 npm6MIT
TDQS
B3.3/5.0
Scored across 35 tools
Disambiguation3/5
Most tools divide into clear mobile, webview, and flow groups, but run_flow's op list overlaps with many individual tools (launch_app, screenshot, webview_connect, tap_text), and there are three screenshot-related tools (mobile_take_screenshot, mobile_save_screenshot, webview_screenshot). Descriptions clarify some boundaries, but an agent could easily select a single-step run_flow or the wrong screenshot tool.
Naming Consistency4/5
Snake_case verb_noun naming is used throughout, with clear mobile_ and webview_ prefixes plus flow verbs. Minor inconsistencies exist: the webview group lacks the mobile_ prefix, coordinate suffixes vary (click_on_screen_at_coordinates vs double_tap_on_screen vs long_press_on_screen_at_coordinates), and run_flow/save_flow/list_flows form a separate prefix family.
Tool Count2/5
With 35 tools, this exceeds the 25+ threshold for 'too many' even for an all-in-one mobile/webview/flow server. Several tools could be consolidated, such as the screenshot variants and the overlap between run_flow's op set and individual action tools.
Completeness3/5
App lifecycle, device interactions, screenshots, and webview inspection are broadly covered. However, flows can be saved, listed, and run but not deleted or updated, and some run_flow operations (wait, tap_text, assert_route) have no standalone equivalents, forcing workarounds. These are notable gaps but not fatal.
Maintenance
ActivityMaintained
ResponsivenessNo issues