mobile-simulator-emulator-mcp
Related Servers
Alternatives to mobile-simulator-emulator-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server for mobile automation and development, offering a single API to control iOS and Android devices (simulators, emulators, real devices) through accessibility trees and coordinate-based interactions. It lets AI agents launch apps, tap, swipe, type, capture screenshots, and extract structured data from native mobile apps.2359,714 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with iOS simulators, perform accessibility testing, manage apps, and automate complex iOS workflows.32Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables coding assistants to drive iOS Simulators and Android emulators or USB devices for React Native and Expo work, including taking screenshots, reading app and device logs, opening deep links, installing builds, and launching or relaunching apps. It also supports Android-specific actions such as adb reverse for Metro, opening the dev menu, and tapping or typing on screen.MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server implementation for iOS Simulator control, providing tools for device management, app operations, permissions, system features, and certificate handling.296 npm20MIT
- AlicenseNot gradedqualityBmaintenanceA native Model Context Protocol server that connects AI IDEs and coding assistants to a real Android device or emulator via ADB, enabling cross-app automation, natural-language task execution, UI inspection, screenshots, taps, swipes, text input, and Logcat capture. A companion phonepilot-direct server lets the client itself look at screenshots and drive the phone step by step without needing a separate model API key.Apache 2.0
- AlicenseCqualityCmaintenanceA local-first Model Context Protocol server that enables AI-assisted development through scoped file access, opt-in shell and process execution, Git automation, development pipelines, and optional Windows desktop and Android/ADB tools. It supports streamable HTTP and stdio transports with secure local-only defaults.105MIT
TDQS
Scored across 12 tools
Each tool targets a distinct operation (device management, app lifecycle, permissions, location, push notifications) with no overlap. Descriptions clearly differentiate iOS and Android where needed.
All tools follow the consistent pattern 'mobile_verb_noun' with snake_case. Verbs are action-oriented (list, boot, install, etc.) and noun complements are specific.
With 12 tools, the set covers device and app lifecycle, permissions, location, and push notifications without being excessive or too sparse for the domain of mobile simulation/emulation.
The surface covers core workflows (list, boot, install, launch, terminate, reset, logs, permissions, location, push, erase). Minor gaps like device details or screenshots are not critical but would enhance completeness.