ios-control-mcp
Related Servers
Alternatives to ios-control-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect and control connected iPhones, iPads, and iOS simulators through local Mac tools, including device previews, UI and OCR inspection, builds, and session-bound approvals.1GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables an MCP client on macOS to control a paired iPhone over Wi-Fi or USB through system developer services, without any app installed on the phone. Exposes tools for device discovery and connection, fresh screenshots, taps, drags, Home, app listing and launching, and Unicode text entry.GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables compatible AI apps to observe and control a locally connected iPhone through stdio MCP tools for screenshots, taps, swipes, long presses, text entry, key and button presses, app listing, and app launching, all reusing the console's device session.GPL 3.0
- AlicenseNot gradedqualityDmaintenanceControl a real, physical iPhone from an MCP client, enabling tapping, swiping, typing, reading messages, and navigating apps via Apple's UI-automation channel.1 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables mirroring and controlling the iOS Simulator from MCP clients, providing a live viewer, agent cursor tracking, and token-efficient UI snapshots for automation.871 PyPI2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to control the macOS mouse and keyboard using screenshots and Quartz-based input events, including app switching, clicks, scrolling, text entry, shortcuts, and action-triggered screenshots.3MIT
TDQS
Scored across 11 tools
Each tool maps to a distinct action on the device: capture, tap, swipe, type, button press, app launch, app listing, device listing, status, wait, and network toggle. The only mild overlap is iphone_status versus iphone_list_devices, but the descriptions make the split (current device info vs. enumerate all attached devices) clear enough. Gesture tools (tap/swipe/button) are well differentiated by input mode.
All 11 tools share a uniform iphone_ prefix and snake_case, which makes the set instantly scannable. The suffix convention mixes nouns (status, screenshot, button, wifi_connections) with verbs (tap, swipe, type, wait) and verb_noun (open_app, list_apps, list_devices), a minor inconsistency but still readable and predictable.
Eleven tools is a well-scoped surface for device control automation, with no obvious filler. Each tool covers a primitive the agent would otherwise have to compose awkwardly. The inclusion of iphone_wait and iphone_status shows deliberate scoping to real automation needs rather than padding.
Core interaction primitives (screenshot, tap, swipe, type, buttons, app launch) are present, but the surface lacks element/accessibility inspection, so the agent is blind coordinate-tapping with only screenshots to guide it, and there is no long-press, key-event (return/backspace), or pinch/zoom gesture. Notably, iphone_list_devices explicitly does not select a device and no select_device tool exists, while other tools reference a 'selected device', leaving a real workflow dead end.