Mobai Mcp

io.github.MobAI-AppPublished by GitHub account MobAI-Appv1.2.1Updated Oct 24, 2026

AI-powered mobile device automation for Android and iOS devices, emulators, and simulators

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

MCP server that lets an AI assistant drive Android and iOS devices, emulators and simulators through a batched DSL script, plus screenshots, app management…

What you can do
  • Discover, claim and release devices, and start or stop the automation bridge
  • Take fast low-quality screenshots for visual analysis or save full-quality PNGs to disk
  • List, install, uninstall and debug apps on a device
  • Execute batched DSL scripts covering taps, typing, swipes, waits, assertions, web automation, metrics and screen recording
  • List test projects and run .mob test cases on a chosen device
When to use it
Useful when you want an assistant to operate a real or emulated mobile app hands-on: exploring flows, reproducing bugs, checking UI state, or running existing .mob test cases. It is aimed at local desktop setups where a device is attached.
Requirements
Node.js 18 or newer, the MobAI desktop app running locally with its HTTP API on 127.0.0.1:8686, and a connected Android or iOS device, emulator or simulator. Installed via npx mobai-mcp over stdio; no API keys or environment variables are declared.
Before you install
The assistant can act on devices: installing and uninstalling apps, tapping and typing, and running tests, which changes device state. Device leases are held per session and acting on an unclaimed device auto-claims it. Screenshots and debug logs are written to local disk, and the server talks to a local desktop app on port 8686.

Installation

In SourceWeft

  1. Open Mobai Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MobAI MCP Server

[npm version] [License]

MCP (Model Context Protocol) server for MobAI — AI-powered mobile device automation. Lets AI assistants (Claude Code, Cursor, Windsurf, Cline, and other MCP-compatible tools) control Android and iOS devices, emulators, and simulators via a single DSL-first interface.

How it works

All device interaction is batched through one primary tool: execute_dsl. Instead of exposing dozens of fine-grained tools (tap, swipe, type…), the server accepts a JSON script describing a sequence of actions with predicates, assertions, waits, and conditional branches. This keeps round-trips low and encodes retry/failure strategies server-side.

A small set of companion tools handles device discovery, screenshots, app management, and running .mob test files.

Prerequisites

  • Node.js 18+
  • MobAI desktop app running locally (HTTP API on 127.0.0.1:8686)
  • A connected Android or iOS device, emulator, or simulator

Installation

Claude Code

bash
claude mcp add mobai -- npx -y mobai-mcp

Cursor

Add to .cursor/mcp.json:

json
{  "mcpServers": {    "mobai": {      "command": "npx",      "args": ["-y", "mobai-mcp"]    }  }}

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

json
{  "mcpServers": {    "mobai": {      "command": "npx",      "args": ["-y", "mobai-mcp"]    }  }}

Windsurf / Cline / other MCP clients

The server speaks stdio — use your client's generic MCP configuration:

json
{  "command": "npx",  "args": ["-y", "mobai-mcp"]}

Tools

Device management

ToolDescription
list_devicesList all connected Android and iOS devices
get_deviceGet details about a specific device
start_bridgeStart the automation bridge on a device (required before interaction)
stop_bridgeStop the automation bridge
claim_deviceClaim exclusive use of a device for this session (usually optional: acting on an unclaimed device auto-claims it)
release_deviceRelease one or all device leases held by this session

Screenshots

ToolDescription
get_screenshotFast, low-quality screenshot for LLM visual analysis (may be downscaled; response includes scale factor)
save_screenshotFull-quality PNG to disk for reporting, debugging, or sharing

Apps

ToolDescription
list_appsList installed apps on the device
install_appInstall an .apk or .ipa from a local file path
uninstall_appUninstall an app by bundle ID / package name
debug_appLaunch an app in debug mode and write stdout/stderr to a log file

Automation

ToolDescription
execute_dslPrimary tool. Execute a batch of DSL steps: tap, type, swipe, observe, assertions, web automation, metrics, screen recording, and more.

Test management

Tests are .mob files on disk inside project directories. You read, write, and edit them directly using your assistant's filesystem tools — MobAI watches for changes and updates the UI live. MCP is only needed to discover projects and run tests.

ToolDescription
test_get_activeGet the active test project directory and its .mob cases
test_list_projectsList all known test project directories with their .mob cases
test_runRun a .mob test case on a device (project_dir + case_path + device_id, optional params for ${name} substitution)

Resources

Read these before attempting any device interaction — they describe the DSL schema, action set, predicates, failure strategies, and .mob syntax.

URIPurpose
mobai://reference/device-automationHow to control devices — guide, all DSL actions, predicates, and failure strategies
mobai://reference/testingTesting workflow, rules, error fixes, and .mob script syntax

Example

Open the iOS Settings app, navigate to Wi-Fi, and verify the toggle exists:

json
{  "version": "0.2",  "steps": [    {"action": "open_app", "bundle_id": "com.apple.Preferences"},    {"action": "wait_for", "predicate": {"text": "Settings"}, "timeout_ms": 3000},    {"action": "tap", "predicate": {"text_contains": "Wi-Fi"}},    {"action": "wait_for", "predicate": {"type": "switch"}, "timeout_ms": 3000},    {"action": "assert_exists", "predicate": {"type": "switch"}},    {"action": "observe", "include": ["ui_tree"]}  ]}

Pass this as the commands argument (a JSON string) to execute_dsl along with a device_id from list_devices.

Troubleshooting

"Connection refused" / "Could not reach the MobAI desktop app" — Make sure the MobAI desktop app is installed and running, and the API is reachable at http://127.0.0.1:8686. If you don't have it yet, download and install it from https://mobai.run/download.

"Bridge not running" — Call start_bridge first. The iOS bridge can take up to a minute to come up.

Screenshots not visible — get_screenshot saves to /tmp/mobai/screenshots/ by default and returns the file path. Use your assistant's file-reading capability to view them. DSL observe screenshots are extracted from the response and saved to the same directory.

Development

bash
git clone https://github.com/MobAI-App/mobai-mcp.gitcd mobai-mcpnpm installnpm run buildnode dist/index.js

License

Apache 2.0 — see LICENSE.

Source: README.md at commit 75348bb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts