MCP.Market

Mobile Device MCP server

by srmorete·io.github.srmorete/mobile-device-mcp·v0.1.10·46 stars
No reviews yet

Control iOS and Android devices with multi-device and seamless Native/WebView support.

B80/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

46 stars77 downloads/wk

Reviews

Write one

Nobody has reviewed Mobile Device MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Mobile Device MCP tools (14, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • double_tap

    Double-taps at coordinates on the device screen

  • install_app

    Installs an app on the device from a file on the host: .apk for Android, .app bundle for iOS simulator, .app or .ipa for iOS real device. Replaces existing installs.

  • launch_app

    Launches an app on the device

  • list_apps

    Lists installed apps on the device

  • list_devices

    Lists available mobile devices

  • long_press

    Long-presses at coordinates on the device screen

  • press_button

    Presses a hardware/navigation button on the device

  • run_codewrite action

    Execute test automation code on the device

  • screenshot

    Takes a screenshot of the device screen

  • scroll

    Scrolls on the device screen from start to end coordinates

  • tap

    Taps at coordinates on the device screen

  • terminate_app

    Terminates an app on the device

  • type_text

    Types text on the device

  • uitree

    Returns the UI element tree of the device screen. Off-screen elements are excluded by default; pass include_invisible: true to keep them. With search, results are ranked leaf-first (visible, non-container, smaller area).

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

1 medium
  • Code scan21 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 53 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    bin/cli.js: …eCode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Mobile Device MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,273 servers
Tools
14
the typical server has 7
Tools that change things
7%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
46
more than 94% of 28,534 servers
Downloads a week
77
more than 58% of 11,915 servers with a package

What its tools let an agent do: 12 read · 2 run or deploy

Install Mobile Device MCP in Claude Code, Cursor or VS Code

Runs npx -y @srmorete/mobile-device-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mobile-device-mcp -- npx -y @srmorete/mobile-device-mcp
Add to Cursor

What the publisher says

From the Mobile Device MCP repository's README, as published. We do not edit it. Read it on GitHub

Mobile Device MCP

An MCP server that lets AI agents control iOS and Android devices (tap, scroll, type, take screenshots, read UI trees, and run code). Works with multiple devices at the same time.

How It Works

Three-layer architecture:

  1. On-device servers — Lightweight HTTP servers running on each mobile device (UIAutomator on Android, XCUITest on iOS) that expose the accessibility tree and accept interaction commands.
  2. UI tree filter — Normalizes raw UI trees from both platforms into a unified flat element list.
  3. MCP server — The external interface. Handles device discovery, bootstrapping, port allocation, and proxies requests to on-device servers.

Devices are bootstrapped on first use — the server installs the driver app, allocates a port, starts the on-device server, and polls until it's healthy. After that, all tool calls are proxied over localhost HTTP with per-device bearer token auth.

Tools

run_code

Agents can pass code that looks like UIAutomator or XCUITest, both being Javascript under the hood. The sandbox restricts (Android) potentially dangerous Java operations and only allows (iOS) some XCUITest-ish commands

  • Android: Rhino engine with UIAutomator bindings — uiDevice (click, swipe, find elements, press keys, read display info), By (selectors), Until (wait conditions), console.log()
  • iOS: JavaScriptCore with XCUITest bindings — app (query elements, tap, type, swipe), springboard, device, openApp(bundleId), sleep(ms), console.log()

Both platforms automatically kill runaway scripts (infinite loops) and create a fresh sandbox per call.

Prerequisites

  • Node.js 18+ (for running via npx)
  • Android: Android SDK with adb on PATH
  • iOS Simulator: Xcode with xcrun, simctl
  • iOS Real Device: Xcode with xcodebuild, devicectl, and iproxy (from libimobiledevice)
  • Building from source: Bun runtime, Gradle (Android), Xcode (iOS)

Installation

Claude Code

claude mcp add mobile-device-mcp -- npx -y @srmorete/mobile-device-mcp@latest

Or with custom ports:

claude mcp add mobile-device-mcp -e MDMS_PORT_ANDROID=20000 -e MDMS_PORT_IOS=21000 -- npx -y @srmorete/mobile-device-mcp@latest

Modifying .mcp.json (Cursor, Claude Desktop, etc)

{
  "mcpServers": {
    "mobile-device-mcp": {
      "command": "npx",
      "args": ["-y", "@srmorete/mobile-device-mcp@latest"],
      "env": {
        "MDMS_PORT_ANDROID": "18000",           # optional
        "MDMS_PORT_IOS": "19000"                # optional
      }
    }
  }
}

Building from Source

git clone <repo-url>
cd mobile-device-mcp
bun install

# Build drivers for both platforms and pack tarball
./scripts/build.sh

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Mobile Device MCP: common questions

Is Mobile Device MCP server safe?
Mostly: it is graded B (80/100). Read the Mobile Device MCP safety report
How do I install Mobile Device MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Mobile Device MCP need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Mobile Device MCP maintained?
The last commit was 92 days ago (2026-08-02). The latest release is v0.1.10.
What can I use instead of Mobile Device MCP?
Servers from other publishers that do the same job: Mobile MCP server, MCP Appium - Mobile Development and Automation Server MCP server and Mobilerun MCP server. Compare all Mobile Device MCP alternatives.
How does Mobile Device MCP compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,273 servers); tools 14 (the typical server has 7); tools that change things 7% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Mobile Device MCP

Same job from other publishers: the closest match first, then the best rated.

All Mobile Device MCP alternatives →
  • Mobile
    MCP server for iOS and Android Mobile Development, Automation and Testing
    A
  • MCP Appium - Mobile Development and Automation Server
    MCP server for Appium mobile automation on iOS and Android devices with test creation tools.
    A
  • Mobilerun
    Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.
    A