A
licenseB
qualityB
maintenanceEnables AI assistants to write and run mobile UI tests on Android and iOS simulators via natural language, supporting native and WebView apps without Appium.
38
65 npm
MIT
MCP Appium
Officialby appium
Related Servers
Alternatives to MCP Appium
No user-submitted related servers found.
Related Servers
MobAI MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to automate mobile devices (Android and iOS) through a single DSL interface, supporting actions like tap, type, swipe, and assertions.20193 npm251Apache 2.0- AlicenseAqualityBmaintenanceEnables AI assistants to control mobile and desktop devices with natural language, including running automation tasks, taking screenshots, and managing devices.65 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate Android mobile device testing through Appium, with automatic device detection, screen element inspection, and natural language test scenario execution.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to automate Android and iOS devices, including emulators and physical devices, by capturing screenshots, reading UI accessibility trees, performing touch and text input, and managing app lifecycle and logs.MIT
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive control of iOS simulators and real devices through AI assistants, supporting app management, UI automation, screenshots, media operations, and location simulation for iOS development and testing workflows.8MIT
TDQS
A3.5/5.0
Scored across 32 tools
Disambiguation4/5
Descriptions are detailed and include priority guidance, but several gesture-related tools (appium_gesture, appium_drag_and_drop, appium_perform_actions) and element text retrieval (appium_get_text vs appium_get_element_attribute) overlap. The multi-action tools (session_management, mobile_device_control) require knowing action values, which adds some cognitive load but is well-documented.
Naming Consistency3/5
Most tools use snake_case with an appium_ prefix, but three tools (select_device, prepare_ios_simulator, generate_locators) lack the prefix, and the appium_mobile_ subgroup is inconsistently applied. The naming also mixes noun-only tools (appium_gesture, appium_alert) with verb_noun patterns, making the convention less predictable.
Tool Count2/5
32 tools is heavy for a single server and exceeds the 25-tool threshold where consolidation is typically expected. While many tools cover distinct Appium capabilities, the set could be streamlined by merging related mobile-extension tools or using more action-based composites.
Completeness4/5
The surface covers core mobile automation extensively: device prep, sessions, element finding/interaction, gestures, device control, app lifecycle, permissions, clipboard, keyboard, geolocation, orientation, alerts, screenshots, and recordings. Minor gaps exist for advanced operations like network condition simulation, device log retrieval, biometric simulation, and execute_script, but core workflows are complete.
Maintenance
ActivityActive
ResponsivenessResponsive