mobile-simulator-emulator-mcp
Control iOS Simulators and Android Emulators over MCP to inspect tooling, manage apps/devices, and drive UI for testing.
Check Apple/Android tooling, device counts, and WebDriverAgent status (
mobile_doctor).List, boot, and shut down Simulators/AVDs (physical devices are excluded by this schema).
Install, launch, terminate, reset, and uninstall apps, and fetch bounded app logs.
Grant, revoke, or reset app permissions and set simulated GPS location.
Use simulator/emulator features: iOS push, clipboard, status bar; Android battery, SMS, fingerprint, network, rotation.
Open http/https URLs or allowed deep-link schemes.
Take screenshots and read the native UI hierarchy.
Interact by coordinates: tap, swipe, type text, and press HOME/BACK/ENTER/app-switch/volume keys.
Lets agents inspect, control, and test Google Android Emulators: booting configured AVDs and shutting them down, installing APKs, launching/terminating/resetting apps, UI automation by element or coordinate, screenshots and screen recording, app logs and crash buffers, runtime permissions, simulated location, battery and charging state, network speed/latency profiles, airplane mode, wifi and mobile data toggles, inbound SMS, fingerprints, rotation and orientation, and emulator snapshots.
Provides tools for interacting with Apple's iOS Simulator platform and Apple testing services, including Simulator lifecycle management, Apple privacy-service permission granting, Apple XCTest accessibility audits of the foreground app, iOS Simulator keychain certificate management, APNs payload delivery, and simulated Face ID/Touch ID enrollment and scans.
Lets agents inspect, control, and test Apple iOS Simulators: booting/shutting down and erasing devices, installing, launching, terminating, resetting, and uninstalling apps, UI automation by element or coordinate, alerts, keyboard and lock state, screenshots and screen recording, logs and crash reports, privacy-service permissions, simulated GPS location and waypoint routes, push notifications, biometrics (Face ID/Touch ID), clipboard, status bar overrides, appearance, connectivity, and accessibility settings.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mobile-simulator-emulator-mcp List my available simulators and emulators"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
What it does
Your coding agent can open, tap, type, scroll, and check apps on a local device, through MCP (Model Context Protocol).
56 tools for apps, screen actions, screenshots, logs, location, permissions, and device settings.
Finds buttons by their text, so the agent does not guess screen positions.
Waits and scrolls for you with
mobile_wait_for_elementandmobile_scroll_to_element.Real phones too: iPhones, iPads, and Android phones connected to your Mac (see Physical devices).
Local and safe: no shell access, no telemetry.
Related MCP server: simctl-mcp
How it works
Platform | Uses |
iOS Simulator |
|
Android Emulator | Google |
Physical iPhone or iPad |
|
Physical Android phone | Google |
It runs over stdio. Add --listen for HTTP on your own machine only.
Requirements
macOS with Xcode 15 or newer.
Node.js 22.18+ or 24.2+.
For Android: Android SDK Platform Tools (
adb). Add the Android Emulator for virtual devices.At least one device: an installed iOS Simulator runtime, an Android virtual device, or a connected phone.
Check the native tools:
xcrun simctl list devices # iOS Simulators
xcrun devicectl list devices # iPhones and iPads
adb devices -l # Android emulators and phones
emulator -list-avds # Android virtual devicesConnect your agent
The commands below run the server straight from GitHub. On first use, npm clones, installs, and builds it. --allow-git=root is required on npm 12, which blocks git packages by default.
Pi
pi mcp add mobile --description "iOS Simulators, Android Emulators, and real phones: apps, screenshots, taps, typing. Load the mobile-mcp skill first." -- npx -y --allow-git=root github:gitsoufiane/mobile-simulator-emulator-mcp
pi mcp listThe first iOS UI call can take several minutes, and Pi's default per-request timeout is 60 seconds. Add "timeout": 300 to the mobile entry in ~/.pi/agent/mcp.json.
Claude Code
claude mcp add --scope user mobile -- npx -y --allow-git=root github:gitsoufiane/mobile-simulator-emulator-mcp--scope user makes the server available in every project. Without it, Claude Code adds it to the current project only.
Codex
codex mcp add mobile -- npx -y --allow-git=root github:gitsoufiane/mobile-simulator-emulator-mcpCodex stops a tool call after 60 seconds and a server start after 10 seconds by default. The first iOS UI call and the first server start take longer. In ~/.codex/config.toml, add these two lines directly under the [mcp_servers.mobile] table that the command created:
tool_timeout_sec = 300
startup_timeout_sec = 120For a physical iPhone or iPad, select your work or Personal Team with mobile_set_ios_team({ teamId: "<TEAM_ID>" }) after connecting. To set a default at server startup instead, pass --env MOBILE_MCP_IOS_TEAM_ID=<TEAM_ID> after the server name mobile and before --; all three CLIs accept this order.
Other MCP clients
Clients that run local stdio servers can use this entry:
{
"mcpServers": {
"mobile": {
"command": "npx",
"args": ["-y", "--allow-git=root", "github:gitsoufiane/mobile-simulator-emulator-mcp"]
}
}
}To run a local build instead, build from source and point the client at dist/src/index.js:
git clone https://github.com/gitsoufiane/mobile-simulator-emulator-mcp.git
cd mobile-simulator-emulator-mcp
npm ci --ignore-scripts
npm run build{
"mcpServers": {
"mobile": {
"command": "node",
"args": [
"/absolute/path/to/mobile-simulator-emulator-mcp/dist/src/index.js"
]
}
}
}Restart the client after you change its configuration.
App, media, and certificate paths must be beneath the server's working directory. Clients that start the server in your project need no extra setting. Otherwise, set the client's cwd to your project, or set MOBILE_MCP_APP_ROOT.
HTTP mode (--listen)
For clients that connect by URL instead of starting a process:
node dist/src/index.js --listen 3000
# ready on http://127.0.0.1:3000/mcpThe listener binds to 127.0.0.1 only and has no authentication, so it has the same trust model as stdio. It rejects with HTTP 403 any request whose Host or Origin is not 127.0.0.1, localhost, or [::1], so a web page cannot reach it through DNS rebinding. All sessions share one set of device controllers and one WebDriverAgent process.
Add the agent skill
This repository includes the Agent Skills skill skills/mobile-mcp. It tells the agent how to call the tools in Pi, Claude Code, and Codex, how to read the server instructions, and how to treat real phones safely. It helps most in Pi, which shows only one line of MCP server instructions to the model.
Install the skill
Pi: install this repository as a Pi package. Pi clones it, loads skills/mobile-mcp, and lists it in pi list and settings.json. pi update pulls new versions from GitHub.
pi install git:github.com/gitsoufiane/mobile-simulator-emulator-mcpClaude Code and Codex: use the skills CLI:
npx skills add gitsoufiane/mobile-simulator-emulator-mcp --skill mobile-mcp -g -a claude-code codexThis puts the skill in ~/.agents/skills/mobile-mcp (Codex) and ~/.claude/skills/mobile-mcp (Claude Code). The skills CLI sends install telemetry; set DO_NOT_TRACK=1 to turn it off. Do not also install it for Pi this way: Pi reads ~/.agents/skills too and warns about the duplicate name.
Restart the agent, or run /reload in Pi.
Use the MCP with the skill
Connect the server with the command for your agent (see Connect your agent).
Install the skill.
Ask for the task in plain words, for example: "Open Settings on my connected iPhone and take a screenshot." The agent loads the skill when the task matches.
To force the skill, start the request with
/skill:mobile-mcpin Pi or/mobile-mcpin Claude Code. In Codex, type$mobile-mcpor pick it from/skills.
With the skill, the agent checks that the mobile tools exist (and gives you the setup command if not), reads the server instructions, and asks you before it installs, uninstalls, or resets anything on a real phone.
Physical devices
mobile_list_devices marks real devices with physical: true. They support app install, launch, terminate, uninstall, and app lists, plus screenshots, UI reading, taps, swipes, typing, keys, alerts, orientation, and URLs. Tools that need simulator or emulator features (boot, shutdown, erase, push, clipboard, status bar, permissions, location, media, SMS, sensors, snapshots, and similar) return a clear error.
Android: turn on USB debugging, connect by USB or adb pair/adb connect, and accept the prompt on the phone.
iPhone or iPad (Xcode 15 or newer):
Turn on Developer Mode on the device, connect it, and trust this Mac.
Call
mobile_set_ios_teamwith{ "teamId": "<TEAM_ID>" }, using your work or Personal Team's 10-character Apple Developer team ID from Xcode. A free Personal Team works. Alternatively, setMOBILE_MCP_IOS_TEAM_IDas the server's default.The first UI call builds, signs, and installs WebDriverAgent on the device. Xcode registers the bundle ID
local.mobilemcp.<TEAM_ID>.WebDriverAgentRunnerin that team.On the device, open Settings > General > VPN & Device Management and trust the developer certificate. Keep the device unlocked.
To switch teams, call mobile_set_ios_team again with the other team's ID. The selection applies to all physical iOS devices on this server until it restarts; it does not change your Xcode accounts or saved server configuration. After a restart, MOBILE_MCP_IOS_TEAM_ID is the default again. Changing teams waits for the current UI action to finish, then stops WebDriverAgent. The next UI call builds, signs, and installs it under the selected team. Selecting a team does not check certificates or provisioning; Xcode checks those during the build. Sign in to the matching Apple account in Xcode first.
Notes for physical iOS devices:
WebDriverAgent listens only on the private CoreDevice tunnel address, not on your Wi-Fi network.
App installs need a device-signed
.app.App logs and crash logs are not available; use Xcode or Console.
A free Personal Team profile expires after 7 days. The next UI call then rebuilds WebDriverAgent, and you may need to trust the certificate again.
Agent workflow
The server sends this guidance to the agent as MCP instructions. The first iOS UI call builds WebDriverAgent through Xcode and can take several minutes; later calls reuse it.
Call
mobile_doctor.Call
mobile_list_devicesand keep the returned ID.Boot a shutdown Simulator or virtual device if needed.
Install and launch the app. Use
mobile_list_appsto look up the exact bundle ID or package name instead of guessing, andmobile_get_foreground_appto confirm the launch landed.Set the permissions or simulated location that the scenario needs (Simulators and emulators only).
Call
mobile_list_elementsbefore using coordinates. It returns compact elements with tap-readycentercoordinates; passqueryto find one element. Usemobile_take_screenshotfor visual context andmobile_get_ui_treeonly when you need the full native hierarchy.Interact with
mobile_tap,mobile_swipe,mobile_type_text, andmobile_press_key.Re-read the UI tree or screenshot after each state-changing action. Use
mobile_wait_for_elementto wait for a screen to load instead of sleeping, andmobile_scroll_to_elementto reach rows that are not on screen yet.Collect
mobile_get_logswhen a workflow fails. Usemobile_reset_apponly when a clean app state is required.
Example requests
Once connected, an agent can handle requests such as:
“List my available simulators and emulators, then boot the shutdown iPhone.”
“On my connected iPhone, open Settings and take a screenshot.”
“Install the Android debug APK, launch it, and take a screenshot.”
“Open
myapp://checkout/123, inspect the UI tree, and tap Continue.”“Set the emulator location to San Francisco and test the nearby-results screen.”
“Collect the last five minutes of logs for
com.example.app.”“Reset the test app, grant location permission, and rerun the onboarding flow.”
Destructive tools run without an extra MCP-side confirmation. Configure this server only for trusted agents and disposable app and device data. On a physical device, they change real data on that phone.
Tools
Tool | Purpose |
| Check native tools, device counts, and WDA status |
| List iOS Simulators, Android Emulators, configured AVDs, and connected physical devices |
| Select a work or Personal Team by Team ID for physical iOS signing until the server restarts |
| Boot and wait for an iOS Simulator or Android AVD |
| Shut down a running target without deleting data |
| Install |
| Launch an app by bundle/package ID, optionally with a locale, iOS arguments/environment, or Android intent extras |
| Stop an app without clearing data |
| List installed bundle IDs/package names (user apps by default) |
| Report which app (and Android activity) is in front |
| Return bounded logs for one installed app |
| Clear Android app data or uninstall an iOS app |
| Grant/revoke Android runtime permissions or grant/revoke/reset allowlisted iOS privacy services |
| Set simulated GPS coordinates; iOS also clears the simulation or moves along a waypoint route |
| Send a ≤4096-byte APNs payload to an iOS Simulator app |
| Add photos, videos, or vCard contacts to the device library |
| Uninstall an app and its data |
| Shut down and erase an iOS Simulator |
| Replace iOS Simulator pasteboard text |
| Read iOS Simulator pasteboard text |
| Override or clear typed iOS status-bar values |
| Switch light/dark appearance on either platform |
| Reduce motion and screen reader (VoiceOver/TalkBack) on both; iOS Dynamic Type, contrast, transparency; Android font scale |
| Set Android Emulator battery capacity and charging state |
| Deliver a simulated inbound Android SMS |
| Touch/remove an enrolled Android Emulator fingerprint |
| Set Android Emulator speed and latency profiles |
| Toggle Android Emulator airplane mode, wifi, or mobile data |
| Rotate an Android Emulator clockwise |
| Set an absolute orientation on either platform; Android |
| Open an allowed URL or deep link |
| Return a PNG image directly to the client |
| Return iOS JSON or Android XML UI hierarchy |
| Return compact labeled/interactive elements with tap-ready center coordinates |
| Tap, double tap, or long press an element found by label, identifier, value, or type |
| Wait until an element is visible or gone, retrying transient screen-read errors (timeout up to 60 s) |
| Swipe in a direction until an element's center is on screen; stops at the end of the content |
| Double tap validated coordinates |
| List, accept, or dismiss the visible iOS alert, optionally by button label |
| Hide the software keyboard |
| Lock or unlock the screen and report the resulting state |
| Enroll/unenroll iOS Face ID or Touch ID and deliver matching or failing scans (Xcode 27) |
| Record an |
| Return an app's Android crash buffer or summarized iOS Simulator crash reports |
| Run Apple's XCTest accessibility audit on the foreground iOS app |
| Add a root or regular certificate to, or reset, the iOS Simulator keychain |
| List, save, load, or delete Android Emulator snapshots |
| Simulate an inbound Android call and accept, hold, busy, or end it |
| Set Android Emulator acceleration, gyroscope, light, proximity, and other sensors |
| Set or clear the Android Emulator HTTP proxy |
| Return screen width, height, orientation, and density |
| Tap validated coordinates |
| Press and hold validated coordinates |
| Swipe between validated coordinates |
| Type into the focused field |
| Press HOME/BACK/ENTER/app-switch/volume keys as supported; Android |
Device IDs
iOS Simulator or device:
ios:<UDID>Running Android emulator or phone:
android:<serial>, such asandroid:emulator-5554Shutdown Android AVD:
android-avd:<AVD-name>
Always use IDs from the latest mobile_list_devices result.
Configuration
Variable | Default | Meaning |
| MCP process working directory | Apps, media, and certificates are read, and recordings are written, only beneath this directory |
| empty | Comma-separated extra deep-link schemes; |
|
| Set to |
| none | Default Apple Developer team ID for physical iOS signing; |
| executable lookup | Android SDK location |
Security model
stdio by default. The optional
--listenHTTP transport binds to127.0.0.1only and rejects non-loopbackHost/Originheaders (DNS-rebinding protection). There is no remote listener or authentication surface.No arbitrary shell,
adb shell, orsimctl spawntool is exposed.Native commands use argument arrays, explicit Android serials, timeouts, and output limits.
Device creation/deletion, raw native-command passthrough, and arbitrary host shell access are not supported.
Curated destructive operations—including app reset/uninstall and iOS Simulator erase—execute without per-call confirmation. The MCP client configuration is the trust boundary. On a physical device these change real data on that phone.
Emulator-console and simulator-only commands are refused before they reach a physical device.
URL schemes, device identifiers, app IDs, permissions, coordinates, environment profiles, durations, push payloads, locales, launch environment names, intent-extra keys, proxy addresses, snapshot names, and file paths are validated.
Recordings are written only as new
.mp4files inside an existing directory beneathMOBILE_MCP_APP_ROOT; existing files are never overwritten.The Android emulator console reports failures as
KO:with exit code 0. Every console call checks for it, so a rejected command is an error, never a silent success.WebDriverAgent is contacted only at
127.0.0.1:8100for Simulators, or at the CoreDevice tunnel address for a physical iOS device.
Treat this server like any local developer tool: it runs with the MCP client's operating-system permissions and can interact with apps displayed in test devices.
Limits
One iOS device (Simulator or physical) can own the WebDriverAgent process at a time, across all stdio or HTTP sessions of one server process. Android can run concurrently.
mobile_list_elementskeeps elements that have a label, identifier, or value, or that are interactive. Layout containers and iOS keyboard keys are omitted; usemobile_get_ui_treewhen you need them.mobile_get_ui_treeand Android input need the screen on and unlocked. A sleeping Android Emulator makesuiautomator dumpfail, and the server reports that as an error rather than returning an empty tree.mobile_set_accessibilitysplits by platform:contentSize/increaseContrast/reduceTransparencyare iOS-only,fontScaleis Android-only.reduceMotionandscreenReaderwork on both; on iOS they need Xcode 27devicectl, and Android TalkBack must be installed in the emulator image.Android
mobile_set_orientationlocks rotation; passautoto restore sensor rotation. iOS usesdevicectlon Xcode 27 (works on the portrait-only home screen) and falls back to WebDriverAgent on older Xcode.mobile_record_screenrecords for 1–180 s. The defaultrecordaction blocks; useaction: "start", act, thenaction: "stop"to record your own taps. Androidscreenrecordhas no audio and stops at 180 s.mobile_get_crash_logson iOS reads~/Library/Logs/DiagnosticReportsand keeps only reports whosecoalitionNamenames the target Simulator.The Android proxy is applied by the emulator process on the Mac, so use a Mac-side address such as
127.0.0.1:8888, not the guest alias10.0.2.2.Android
mobile_set_lockunlock dismisses only the default swipe keyguard; a PIN, pattern, or password stays locked and the tool reports an error.Android per-app locale (
mobile_launch_applocale) needs Android 13+ and persists until you launch withlocale: "system".mobile_list_appsreturns Android package names without display labels; iOS returnsCFBundleDisplayNamewhen the app declares one.Android
input textsupports printable ASCII only. iOS typing supports Unicode through WDA.UI trees depend on apps exposing useful accessibility labels/identifiers.
Trees and logs over one million characters return
truncated: true; treat the result as incomplete.Android Emulator has no official command to clear its last GPS fix; the release gate restores it to
0,0.Android AVD wipe is a boot-time option, so
mobile_erase_deviceis iOS-only.Clipboard, cosmetic status-bar control, alerts, Face ID/Touch ID, keychain, accessibility audits, and location routes are iOS-only in the installed official tools. SMS, fingerprint, network profiles, battery state, snapshots, calls, sensors, proxy, and
mobile_rotateare Android-only.Android clipboard: the platform has no shell clipboard command (
cmd clipboardreports no implementation), so clipboard stays iOS-only.Simulated push delivery is iOS-only. Android FCM requires Firebase rather than
adb.Apple exposes no supported command for Simulator network conditioning; it remains out of scope.
App-container host paths, iCloud sync, and device create/clone/delete/rename stay out of scope: they leak host paths or manage fleets rather than test a running device.
Android foldable posture, multi-display, and screen-size overrides, plus iOS Siri, remain unimplemented.
MCP resources, prompts, and completions are not implemented. Device state changes too quickly to cache as resources, and every workflow here is better expressed as an explicit tool call.
Simulators and emulators do not reproduce all real-device sensors, performance, or hardware behavior.
Troubleshooting
mobile_doctor reports a missing Android command
Set ANDROID_SDK_ROOT or ANDROID_HOME to the Android SDK directory and ensure its platform-tools and emulator directories are installed. You can also add both directories to PATH.
iOS UI calls time out on first use
WebDriverAgent may need several minutes to compile through Xcode. Set MOBILE_MCP_SHOW_XCODE_LOG=1 in the MCP environment to send detailed build logs to stderr.
App installation is rejected
The artifact must resolve beneath the agent project's working directory, or beneath MOBILE_MCP_APP_ROOT when explicitly configured. Android requires an .apk file. iOS requires a built .app directory: a Simulator build for a Simulator, or a device-signed build for a physical device.
A deep link scheme is rejected
http and https are enabled by default. Add custom schemes as a comma-separated environment value, for example MOBILE_MCP_URL_SCHEMES=myapp,example-beta.
A device ID is rejected
Call mobile_list_devices again and use its exact current ID.
A physical iPhone or iPad fails to start WebDriverAgent
xcodebuild failed with code 65: setMOBILE_MCP_SHOW_XCODE_LOG=1and read the Xcode log. The usual causes are an untrusted developer certificate (Settings > General > VPN & Device Management) or a locked device.Not authorized for performing UI testing actions: the device locked while WebDriverAgent was running. Unlock it, stop the agent withmobile_terminate_appandappIdlocal.mobilemcp.<TEAM_ID>.WebDriverAgentRunner.xctrunner, then retry.
Development and release checks
npm run check
npm run live
npm run live:deep
npm run live:tools
npm run live:extended
npm run live:destructive
npm audit --omit=devEvery tool must pass a live test before you push. Boot one iOS Simulator and one Android Emulator, then run all the commands above. Together the live* gates cover the 55 device tools. Also test mobile_set_ios_team with your work and Personal Team IDs on a physical iOS device, then run a UI call after each selection to verify signing.
npm run live:extended exercises every 0.5.0 tool on both platforms against Settings and Safari and restores each change: locale, launch arguments/extras, element taps, keyboard, orientation (including a landscape tap beyond the portrait width), double tap, lock, recording, crash logs, snapshots, calls and console KO: errors, sensors, proxy, reduce motion, TalkBack/VoiceOver, the notification shade, Face ID, alerts, and the accessibility audit.
npm run live:tools covers the app-discovery, appearance, accessibility, screen-info, and long-press tools, and asserts that platform and coordinate rejections still reject. It exercises Android in full and skips the iOS paths that would take over the Simulator with WebDriverAgent; set MOBILE_MCP_LIVE_WDA=1 to include them.
npm run live performs fast screenshots, UI-tree reads, and HOME input on both platforms. npm run live:deep uses the MCP stdio protocol to manipulate Android and iOS Settings, exercise a spare iOS boot/shutdown when available, set simulated locations, collect app logs, round-trip the iOS clipboard, override/clear the iOS status bar, change/restore Android battery and network profiles, rotate Android four times, remove a fingerprint touch, type and swipe, open https://example.com, verify screenshots and UI changes, exercise rejected inputs, and restore managed state.
npm run live:destructive tests the tools that install, delete, or erase. It never touches your devices: it creates a throwaway iOS Simulator and Android Emulator (AVD mobile_mcp_disposable), builds a tiny test app for each, and deletes all of them at the end. It covers boot, shutdown, install, uninstall, reset, permissions, push, media, keychain, SMS, connectivity, and erase. It needs Xcode, Android build-tools 37.0.0, the android-36 platform, the android-37.0 Play Store 16 KB system image, a JDK (keytool), and openssl. It takes a few minutes, mostly for the emulator cold boot.
Official references
The implementation and tool limits were checked against:
MCP tool specification for strict inputs, structured results, annotations, errors, and the client-side trust model for sensitive operations.
MCP transport specification for Streamable HTTP, loopback binding, and
Originvalidation against DNS rebinding.Apple Xcode command-line tool reference and the installed
xcrun simctl helpfor Simulator lifecycle, logs, privacy, location, push, and screenshots.Android Debug Bridge, Logcat, and Emulator console for app state, permissions, logs, location, and emulator lifecycle.
See PLAN.md for the approved scope and release gates.
Available Tools
12 toolsmobile_boot_deviceBoot Mobile DeviceAIdempotent
Boot an iOS Simulator or configured Android virtual device and wait until it is ready.
Inputs: device (required), timeoutSeconds.
mobile_erase_deviceErase iOS SimulatorADestructive
Shut down and erase all content and settings from an iOS Simulator. Android online wipe is not supported by the official emulator console.
Inputs: device (required). Returns: device, erased
mobile_get_logsGet Mobile App LogsARead-onlyIdempotent
Return bounded recent logs for one installed app. Android filters by package UID; iOS filters by the app executable.
Inputs: appId (required), device (required), maxLines, sinceMinutes. Returns: logs, appId, device, platform, +1 more
mobile_install_appInstall Mobile AppADestructiveIdempotent
Install an APK on an Android Emulator or an .app directory on an iOS Simulator. Paths are confined beneath MOBILE_MCP_APP_ROOT.
Inputs: path (required), device (required).
mobile_launch_appLaunch Mobile AppBIdempotent
Launch an installed app by iOS bundle ID or Android package name.
Inputs: appId (required), device (required).
mobile_list_devicesList Mobile DevicesARead-onlyIdempotent
List available iOS Simulators, running Android Emulators, and configured Android virtual devices. Physical devices are excluded.
Inputs: no named parameters.
mobile_reset_appReset Mobile App StateADestructive
Clear Android app data or uninstall an iOS app. Reinstall the iOS app with mobile_install_app afterward.
Inputs: appId (required), device (required). Returns: appId, reset, device, result
mobile_send_pushSend iOS Simulator PushA
Send an APNs JSON payload to an installed iOS Simulator app. Android FCM has no equivalent adb command.
Inputs: appId (required), device (required), payload (required). Returns: appId, bytes, device, pushed
mobile_set_locationSet Mobile LocationAIdempotent
Set simulated latitude/longitude on iOS or Android. Clearing the simulated location is supported on iOS only.
Inputs: no named parameters. Returns: action, device, latitude, longitude
mobile_set_permissionSet Mobile App PermissionBDestructiveIdempotent
Grant, revoke, or reset an allowlisted iOS Simulator privacy service; grant or revoke a declared Android runtime permission.
Inputs: appId (required), action (required), device (required), permission (required). Returns: appId, action, device, updated, +1 more
mobile_shutdown_deviceShut Down Mobile DeviceAIdempotent
Shut down a running iOS Simulator or Android Emulator without deleting its data.
Inputs: device (required).
mobile_terminate_appTerminate Mobile AppAIdempotent
Terminate an app by iOS bundle ID or Android package name without clearing app data.
Inputs: appId (required), device (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool targets a distinct operation (device management, app lifecycle, permissions, location, push notifications) with no overlap. Descriptions clearly differentiate iOS and Android where needed.
All tools follow the consistent pattern 'mobile_verb_noun' with snake_case. Verbs are action-oriented (list, boot, install, etc.) and noun complements are specific.
With 12 tools, the set covers device and app lifecycle, permissions, location, and push notifications without being excessive or too sparse for the domain of mobile simulation/emulation.
The surface covers core workflows (list, boot, install, launch, terminate, reset, logs, permissions, location, push, erase). Minor gaps like device details or screenshots are not critical but would enhance completeness.
Related MCP Connectors
Disposable cloud Android emulators for coding agents: run an APK or PR build, tap, type, screenshot.
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.
Cloud iOS simulators and Android emulators your agent can create, drive, and throw away.
Email inboxes, webhook URLs, mock APIs and 170+ tools for coding agents over one MCP connection.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with iOS simulators, perform accessibility testing, manage apps, and automate complex iOS workflows.32Apache 2.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server implementation for iOS Simulator control, providing tools for device management, app operations, permissions, system features, and certificate handling.2920MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server for mobile automation and development, offering a single API to control iOS and Android devices (simulators, emulators, real devices) through accessibility trees and coordinate-based interactions. It lets AI agents launch apps, tap, swipe, type, capture screenshots, and extract structured data from native mobile apps.23Apache 2.0
- AlicenseBqualityCmaintenanceEnables coding assistants to drive iOS Simulators and Android emulators or USB devices for React Native and Expo work, including taking screenshots, reading app and device logs, opening deep links, installing builds, and launching or relaunching apps. It also supports Android-specific actions such as adb reverse for Metro, opening the dev menu, and tapping or typing on screen.20MIT