grogu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROGU_BIND_HOST | Yes | Your Linux host's Tailscale IP address to bind on. | |
| GROGU_DEVICE_IP | Yes | Your iOS/iPadOS device's Tailscale IP address. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
MCP Server providing direct Tailscale control of an unjailbroken iOS/iPadOS device (100.101.102.103): ultra-fast native UI hierarchy dump (XCAXClient_iOS / FastWDA), deterministic Decision API execution, low-level DVT/IORegistry/oslog/pcap/URL-scheme telemetry, and Siri voice task inspection.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ios_statusA | Query device status: Tailscale ports (62078/49152/8100), pairing keys, WDA readiness, and foreground app. |
| ios_ui_dumpC | Dump current UI accessibility hierarchy cleanly in milliseconds. |
| ios_tapC | Tap at screen point coordinates (x, y). |
| ios_tap_elementC | Find a visible UI element by label/name/value and tap its center immediately. |
| ios_swipeC | Swipe from (x1, y1) to (x2, y2) with duration in milliseconds. |
| ios_input_textB | Type text into the currently focused field. |
| ios_keyB | Press hardware button: HOME, VOLUME_UP, or VOLUME_DOWN. |
| ios_launch_appB | Launch an app by alias, Bundle ID, or URL Scheme DeepLink. |
| ios_decision_runB | Execute a deterministic Decision API JSON step list (launch, open_url, tap, tap_selector, wait_selector, swipe, type, button, sleep, reflex). |
| ios_lowlevel_telemetryC | Read low-level iOS/iPadOS telemetry over Tailscale DVT/Lockdownd. Supported kind: summary, processes, ioregistry, schemes, oslog, network, accessibility, dvt_launch, dvt_kill. |
| ios_screenshotB | Capture screen PNG (via WDA if running, else DVT Screenshot). |
| ios_siri_tasksC | Read recent Siri voice commands & execution traces received by the gateway. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.