mobile-mcp
Related Servers
Alternatives to mobile-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables agents and LLMs to interact with native iOS and Android applications and devices via structured accessibility snapshots or coordinate-based taps, supporting simulators, emulators, and real devices.3930,556 npmApache 2.0
- 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

agentlaneofficial
FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to drive and inspect isolated app instances across web, iOS, and Android, with tools for reading screens, running interactions, and capturing screenshots or evidence.-
MCP Appiumofficial
AlicenseAqualityAmaintenanceEnables AI assistants to automate mobile app testing and development for iOS and Android through natural language interactions. Supports intelligent element identification, session management, automated test generation, and comprehensive device interactions including clicks, swipes, screenshots, and app management.3210,465 npm498Apache 2.0- AlicenseCqualityBmaintenanceEnables AI agents to control Android phones, emulators, redroid containers, iOS devices, and cloud-hosted devices through a perceive-act-verify loop of screen reading, taps, gestures, typing, and app launching. Exposes 138 tools for driving screens, elements, and files over adb, Portal APIs, and ios-portal without running ARM-only code on the device.9415 npm1MIT
- 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.92-
TDQS
Scored across 34 tools
Most tools target clearly distinct actions (gestures, app lifecycle, device/cloud management, recording, crashes, logs). The main overlap is mobile_take_screenshot vs mobile_save_screenshot, which is resolved by descriptions (one for visual understanding, one for writing a file), and the list_elements_on_screen vs screenshot pair is also clarified. Boundaries are largely clean.
Nearly all tools use a consistent mobile_ snake_case prefix with a verb_noun pattern (mobile_get_orientation, mobile_launch_app, mobile_list_apps). The lone outlier get_more_tools is an intentional, clearly documented meta-tool for requesting capabilities.
34 tools is heavy and sits above the comfortable range, though the broad domain (device discovery, cloud allocation, app management, gestures, screenshots, recording, crashes, logs) genuinely justifies many of them. A few gesture/screenshot tools could plausibly be consolidated.
The surface covers the full mobile-automation lifecycle: device discovery (local and remote/cloud), app install/launch/terminate/uninstall, input gestures, screen inspection, screenshots, recording, orientation, location, clipboard, logs, and crash reports. No obvious dead ends for the stated purpose.