grogu-mcp
Related Servers
Alternatives to grogu-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to operate a real iPhone locally, completing app and device tasks without jailbreak or extra hardware.1,501AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to operate a real iPhone from a Mac by reading the screen over USB and sending taps, swipes, typing, and app launches over Bluetooth, with every action returning a fresh screenshot so the agent can verify its work. Runs as a local MCP server, so agents can test iOS apps on physical devices and automate everyday phone tasks.38 npm10MIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server that lets AI agents see and operate real iPhones, iPads, and Android devices from a Mac — screenshots, on-device OCR, taps, swipes, typing, app launching, and replayable skills over USB, Wi-Fi, or adb, with nothing installed on the phone. It gates anything that sends, posts, buys, or deletes behind human approval dialogs and private credential entry, backed by a kill switch, policy file, audit log, and a live-view web console.1GPL 3.0
- AlicenseNot gradedqualityBmaintenanceThis MCP server gives AI agents eyes and hands on a real iPhone: they read the screen as a list of elements plus a screenshot, then tap, type, scroll, swipe, answer system permission prompts, press buttons, rotate, and open deep links to test any installed app. It runs over USB or Wi-Fi from Windows, Linux or macOS, with no Mac or Xcode needed, and can be limited to a named set of apps.4MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets LLMs drive a real iPhone through macOS iPhone Mirroring, with tools for screen capture, OCR, taps, typing, and Xcode build/test/install automation.9MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to discover and interact with iOS apps through a local MCP gateway, converting remote Streamable HTTP MCP endpoints into stdio tools. Provides dynamic device discovery, tool schema introspection, and deterministic tool calling for app analysis.-
TDQS
Scored across 12 tools
Each tool maps to a distinct action on the iOS device, with a clear prefix and scope. The only real overlap is ios_tap vs ios_tap_element (coordinate vs element lookup) and ios_status vs ios_lowlevel_telemetry (both report device diagnostics), but descriptions make the boundaries reasonably clear. ios_decision_run intentionally aggregates primitives, which is fine as an orchestrator.
All 12 tools share the ios_ prefix and snake_case, which is highly predictable. However, the ordering is mixed—verb-first (ios_tap, ios_launch_app, ios_input_text) versus noun-first (ios_status, ios_ui_dump, ios_lowlevel_telemetry, ios_siri_tasks)—so it's not a strict verb_noun pattern throughout.
Twelve tools is well within the sweet spot for an iOS automation server. Every tool earns its place: primitives (tap, swipe, text, key), observation (ui_dump, screenshot, status), and higher-level orchestration (decision_run, launch_app, telemetry).
Coverage is strong: observation, low-level input, app launch, batch orchestration, and telemetry are all present. Minor gaps remain—no standalone app terminate/close (only dvt_kill buried in telemetry), no long-press or element-relative swipe, and no query for installed apps.