Mobile Next is an MCP server for controlling and automating native iOS and Android applications on simulators, emulators, and physical devices. It helps agents and developers test apps, complete scripted interactions, automate user journeys, and extract data through accessibility information and screenshots. Its catalogue add-ons connect agent workflows to the server.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mobile-next/mobile-mcp --skill mobile-automationgit clone --depth 1 https://github.com/mobile-next/mobile-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mobile-next/mobile-mcp/mobile-automation)<a href="https://agentmods.dev/skills/mobile-next/mobile-mcp/mobile-automation"><img src="https://agentmods.dev/badge/skills/mobile-next/mobile-mcp/mobile-automation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mobile-next/mobile-mcp/mobile-automation"><img src="https://agentmods.dev/badge/skills/mobile-next/mobile-mcp/mobile-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00058 | $0.00561 |
| Opus 5.5 | $0.00023 | $0.00224 |
| Sonnet 5.5 | $0.00012 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
mobile-automation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Mobile Automation with Mobile MCP
Tools for driving real phones, emulators and simulators. All tools are
prefixed mobile_.
Workflow
- Pick a device. Call
mobile_list_available_devicesand use one of the returned devices for every subsequent call. If no device is available, ask the user to connect one (Android:adb devicesmust show it; iOS: simulator booted or device paired). - See the screen. Prefer
mobile_list_elements_on_screen— it returns the accessibility tree with element labels and coordinates. It is faster, cheaper, and more reliable than screenshots. Fall back tomobile_take_screenshotonly when elements are missing or you need visual confirmation (games, canvas-drawn UI, image content). - Act.
mobile_click_on_screen_at_coordinates,mobile_swipe_on_screen,mobile_type_keys,mobile_press_button(HOME, BACK, VOLUME, ENTER),mobile_launch_app/mobile_terminate_app/mobile_list_apps,mobile_open_url. - Verify after every action. Re-list elements (or re-screenshot) to confirm the UI changed as expected before the next step. Mobile UIs animate; if the expected element is not there yet, wait briefly and check again rather than tapping blind.
Tips
- Click the center of an element's bounds, not its top-left corner.
- To type, first tap the input field, confirm it is focused, then
mobile_type_keys. - Use
mobile_save_screenshotwhen the user wants the image as a file;mobile_start_screen_recording/mobile_stop_screen_recordingfor videos. - App crashed?
mobile_list_crashesandmobile_get_crashfetch crash logs. - Screen size from
mobile_get_screen_size; coordinates are in that space. - Real devices in the cloud (no local hardware):
mobile_login_to_cloud_provider, thenmobile_list_remote_devices/mobile_allocate_remote_device, and release withmobile_release_remote_devicewhen done. See https://mobilenext.ai/docs for details.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 49 lines · 58 tokens per session scan A ed8e37bdea82
mobile-automation is a skill published in the GitHub repository mobile-next/mobile-mcp (9,957 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 561 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-02.
Other skills, from other repositories
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
baguette
Drive and inspect iOS simulators with the baguette CLI: taps, swipes, buttons, typing, screenshots, the accessibility tree, logs, and the conditions an app runs under (location, network, appearance, push, UserDefaults), without opening Xcode. Use when an agent must act on or verify a running simulator — a UI flow…
argent-qa-e2e
Write repeatable QA regression e2e tests from test cases, tickets, or acceptance criteria. Use when the user asks to write, automate, or generate an e2e test or preserve an automated regression scenario, with deterministic setup, stable targets, executable structural or visual evidence, and two consecutive full…
argent-create-e2e
Create, record, edit, replay, or repair reusable Argent e2e test YAML files. Use when the user asks to record, replay, or run an e2e test or a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-e2e. Also use before repeating three or more interactions. For…
mobilewright-cli
Automate iOS and Android apps on simulators, emulators and real devices, explore screens and write Mobilewright tests.