A
licenseNot graded
qualityD
maintenanceGives AI agents the ability to interact with iOS simulators through 21+ tools for mobile app testing.
16,347 npm
MIT
ios-mcp
by emazaheri
Related Servers
Alternatives to ios-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to control real iPhones and simulators on macOS, allowing for UI interaction, testing, and automation.63 npm88MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets an AI agent drive the iOS Simulator in a loop, enabling tapping, typing, swiping, reading the screen via the accessibility tree, and verifying app state.14MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to control iOS simulators through WebDriverAgent, supporting taps, swipes, typing, screenshots, recording, and app actions with a real-time dashboard for visual feedback.36Apache 2.0
Argentofficial
AlicenseAqualityAmaintenanceEnables AI assistants to interact with iOS Simulators and Android Emulators, allowing autonomous app development, UI interaction, profiling, and debugging through natural language.762,880Apache 2.0- AlicenseAqualityAmaintenanceEnables AI coding agents to review Swift code, scaffold new iOS apps, and build, test, and preview them in the Xcode Simulator using local Apple guides and source references.3634MIT
TDQS
A3.7/5.0
Scored across 31 tools
Disambiguation5/5
Each tool has a clearly distinct purpose. Screen-reading tools are differentiated by whether you need refs (observe), hidden elements (find), pixel layout (screenshot), or raw text (read_text). Interaction tools are gesture-specific with no meaningful overlap.
Naming Consistency4/5
The ios_ prefix is consistent, but the action part varies: most are verb_noun (tap, scroll, launch_app), but there are verb phrases (wait_for, set_device_state), bare verbs (halt, resume), and a noun (doctor). This is mostly predictable but not uniform.
Tool Count3/5
31 tools is heavy, but the domain of iOS automation is broad, requiring separate tools for device management, session control, UI observation, gestures, and app operations. Still, the count is above the typical well-scoped range, making it borderline.
Completeness4/5
The surface covers the main automation lifecycle: session, devices, apps, UI inspection, interaction, alerts, permissions, and diagnostics. Minor gaps like app uninstall or springboard manipulation are absent, but agents can work around them.
Maintenance
ActivityMaintained
ResponsivenessNo issues