Limrun

Returns latest screenshot and Android UI hierarchy snapshot.

android-screenshot-and-element-tree

Open a URL or deeplink on the Android instance.

android-open-url

Perform a list of actions on the Android emulator. Use it to carry out UI test steps on the emulator screen. Actions run only inside the disposable cloud emulator the user created; they cannot reach the user's own devices, accounts, or files. android-open-url opens URLs and deeplinks. React Native apps in Expo Go open through android-open-url with the public "exp://" URL; confirm the app is running before the action list. Available action kinds are: tap, setText, pressKey, scrollScreen, scrollElement, findElement, openUrl, startRecording, stopRecording, wait. Actions run strictly in the order they are listed. stopRecording accepts an optional presignedUrl to upload the completed recording to; otherwise the recording stays on the emulator and the result says where. Android selectors must match attributes from the UI hierarchy XML. Use the selector object with these fields: - resourceId: matches the XML "resource-id" attribute - text: matches the XML "text" attribute - contentDesc: matches the XML "content-desc" attribute - className: matches the XML "class" attribute - packageName: matches the XML "package" attribute - index: matches the XML "index" attribute - clickable, enabled, focused: match the corresponding XML boolean attributes - boundsContains: matches any element whose bounds contain the provided x,y coordinate Example XML node: <node index="3" text="Chrome" resource-id="" class="android.widget.TextView" package="app.lawnchair" content-desc="Chrome" clickable="true" enabled="true" focused="false" bounds="[533,1222][706,1422]" /> Example selectors for that node: { "text": "Chrome", "className": "android.widget.TextView", "packageName": "app.lawnchair" } { "contentDesc": "Chrome", "clickable": true } For example if you want to dismiss the developer dialog in Expo Go by clicking "Continue" button, use a tap action like: { "kind": "tap", "selector": { "className": "android.widget.Button", "text": "Continue", } } Prefer selector-based targeting whenever the XML tree exposes a stable element. Combine multiple selector fields to make matches specific. Do not use XML attribute names directly in the selector object; for example use "resourceId" instead of "resource-id" and "contentDesc" instead of "content-desc". For tap, use exactly one targeting mode: - selector: best when the element is present in the XML tree - x and y: only when you already know the exact screen coordinates For setText, prefer selector or coordinates that identify the input field to update. For scrollElement, provide a selector for the container to scroll. Use findElement when you want to check whether a selector matches anything before acting on it. Example action list: [ { "kind": "tap", "selector": { "text": "Chrome", "className": "android.widget.TextView", "clickable": true } }, { "kind": "wait", "duration": 1000 } ] Keep action lists short and focused, but include enough actions to complete the task when filling forms or stepping through a flow. You can call this tool multiple times for longer interactions. If you expect the UI to change after your actions, add a wait action so the returned screenshot reflects the final state. This tool returns the per-action results and a screenshot; call android-screenshot-and-element-tree when you need the element tree. In Expo Go, you can refresh the app by pressing capital R twice, for example two pressKey actions with key "R".

android-use

Create a cloud Android emulator and wait until it is ready. Returns the instance ID to pass to the android-* tools. Pre-install apps by asset name (see list-apps) or public APK URL.

create-android-emulator

Create a cloud iOS simulator and wait until it is ready. Returns the instance ID to pass to the ios-* tools. Pre-install apps by asset name (see list-apps) or public URL. The app must be a simulator build whose ".app" folder is archived into a tar.gz or zip archive.

create-ios-simulator

Delete an iOS simulator or Android emulator by ID. Instances also stop on their own after the inactivity timeout.

delete-instance

Get the full step-by-step procedure for Limrun work the MCP tools do not cover (builds, local files), as an agent skill for the lim CLI. Available skills: limrun-xcode: Build and sign iOS apps with lim xcode on a remote Xcode sandbox. limrun-gradle: Build Android APKs with lim gradle on a remote build sandbox. limrun-xcode-bazel: Build iOS apps with Bazel remote build execution on Limrun. limrun-expo-development: Develop and run Expo apps against Limrun simulators and emulators.

get-agent-skill

Get the current state of an instance by ID.

get-instance-status

Install an app from the organization's Limrun asset storage on a running instance. iOS installs also launch the app.

install-app

Open the Limrun device panel to choose or create an iOS simulator or Android emulator. Opening the panel does not create a device.

open-devices