mobile-mcp
Related Servers
Alternatives to mobile-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to drive real Android devices or emulators by reading the live accessibility tree, acting on UI nodes instead of coordinates, verifying every action, and typing Unicode text.21 npmApache 2.0
- AlicenseBqualityDmaintenanceEnables AI agents to inspect, log, and control React Native apps on Android emulators or iOS simulators, including UI tree, tap, scroll, and hot reload.22989 npm5MIT
- 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-

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.20314 npm247Apache 2.0- AlicenseBqualityBmaintenanceEnables AI agents to control Android devices and emulators through direct UI interaction, allowing app navigation, automated testing, and real-world task execution via ADB without computer vision or scripts.182MIT
- AlicenseNot gradedqualityAmaintenanceControls Android and iOS devices from AI agents through a token-efficient MCP server, enabling observation, tapping, typing, gestures, navigation, assertions, and safety-gated actions.MIT
TDQS
Scored across 39 tools
Most tools have clearly distinct purposes, but a few near-overlaps exist among app-launching tools (mobile_launch_app, mobile_launch_and_ready, mobile_ensure_app) and between mobile_take_screenshot and mobile_save_screenshot. Descriptions are detailed enough to disambiguate with care, so agents should rarely misselect.
All tools follow the consistent mobile_verb_noun pattern, with clear verbs like list, get, set, launch, click, swipe, and take. Even compound actions like mobile_launch_and_ready and prepositions like on_screen are used consistently across the set, making the naming predictable and readable.
At 39 tools, this is well above the 25-tool threshold for 'too many' even for a broad mobile automation domain. While each tool has a specific purpose, the sheer number risks overwhelming an agent and suggests some tools could be consolidated (e.g., combining screenshot save/take or merging device listing variants).
The tool set covers the full mobile lifecycle: device discovery/reservation, app management (install, launch, terminate, ensure), UI interaction (clicks, gestures, typing), screenshots, orientation, location, clipboard, logs, crash reports, screen recording, and a batch execution tool. There are no obvious dead ends or missing critical operations for the stated purpose.