Drive real devices from your AI Coding tool. Embed a client SDK (Unity, Godot, Flutter, iOS/macOS, Android, React Native, Web) in your app, then capture screenshots, traverse the UI tree, inject taps and key events, and run automated test tasks on the physical device over a secure relay.
Scored across 6 tools
Each tool has a distinct purpose: list_devices for enumeration, device_status for connectivity, device_ping for latency, device_detail for tokens/connect info, list_tasks for task discovery, and run_task for execution. No overlap or ambiguity.
Naming follows a predictable pattern with prefixes like list_, device_, and run_. The only minor deviation is device_detail not being a verb, but the pattern is consistent enough to be easily understood.
Six tools is well-scoped for a debug relay server: device management, status checks, task discovery, and execution. Each tool earns its place without redundancy or bloat.
The surface covers the full lifecycle: device discovery, connectivity checks, latency measurement, detailed info retrieval, task manifest listing, and task execution. No obvious gaps for the stated purpose.
Full info for one device, including its clientToken and a ready-to-paste Unity connect snippet. Only call this when the user explicitly asks for the token or connect instructions.
Inputs: device (required).
Round-trip ping to the connected device; measures relay + device latency.
Inputs: device.
Check whether the target device is connected to the relay.
Inputs: device.
List the device token pairs this connection can drive (name, sid, region, online). Call this FIRST; when several devices exist, ask the user which one to use and pass its name or sid as the "device" argument on subsequent tool calls. Tokens are NOT included — use device_detail when the user asks for connect instructions.
Inputs: no named parameters.
Discover what the connected device client can do: returns its task manifest (task types with descriptions and payload schemas) as reported by the device build. Call this before run_task when unsure which task types exist.
Inputs: device.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.
Drive real Android & iOS devices and web browsers from natural language for mobile + web QA. 290+ tools across device control, app management, automation sessions, browser automation, and flow recording / replay. Bearer-auth — get a token at robotactions.com → Profile → API Tokens.
Cloud iPhones and Macs with Xcode for AI agents: build, run and test iOS apps, use the screen.
Add one secure layer between your agents and this server.
