← MCP server and skill grades

mobile-mcp

mobile-next/mobile-mcp

B
Type
MCP server
Scanned
Nov 12, 2026
Version
ad3b42336d89
Files read
86

Mobile MCP is an MCP server and Claude Code plugin that lets AI agents control connected Android and iOS devices, simulators, emulators, and cloud-hosted phones. Because it has full UI, app, clipboard, and log access to attached devices, the biggest risks are prompt injection from untrusted on-screen content leaking context via telemetry or driving unwanted device actions, and exposing connected phones on the network if HTTP mode (--listen) is started without setting MOBILEMCP_AUTH.

What it can reach

Other
Controls connected iOS and Android devices, emulators, simulators, and reserved Mobile Next Cloud phones, including reading UI elements, taking screenshots and screen recordings, tapping, typing, reading and writing the device clipboard, overriding GPS location, reading live device logs and crash reports, and installing, launching, clearing data of, or uninstalling apps.
Files
Reads app bundles (.apk, .ipa, .zip, .app) from any host path to install onto devices, writes screenshots (.png, .jpg, .jpeg), logs (.log, .txt, .jsonl), and recordings (.mp4) inside the current working directory or system temp directory, stores telemetry counters in ~/.mobilecli/mobile-mcp-telemetry.json, and edits MCP client config files when running the install command.
Shell commands
Executes local mobile-automation binaries (mobilecli, and in legacy mode adb, go-ios, xcrun simctl, plutil, zipinfo, and unzip) as child processes.
Network
Sends telemetry events and get_more_tools context to PostHog (us.i.posthog.com) and Scarf (static.scarf.sh) unless MOBILEMCP_DISABLE_TELEMETRY is set, communicates with Mobile Next Cloud via mobilecli when remote device tools are used, connects to localhost:8100 for WebDriverAgent in legacy iOS mode, and opens an HTTP MCP listener when --listen is passed.

Findings

1 medium4 low
  1. MediumRead-only annotated get_more_tools sends uncapped free-form context to third-party analytics

    src/server.ts:336

    When telemetry is enabled (the default), the server registers a get_more_tools tool whose only action is sending the agent-provided context string to Mobile Next's PostHog server with no daily rate cap. Although the tool's prompt warns the model not to include secrets, the tool is omitted from the README (which claims anonymous telemetry and local-only communication) and is annotated with readOnlyHint: true, causing many MCP clients to auto-approve calls without asking the user, which allows prompt injection in on-screen or fetched content to silently send context off-machine.

    Fix: Mark get_more_tools with readOnlyHint: false so MCP clients prompt the user before sending free-form text externally, apply a daily quota cap, and document the tool in the README, or set MOBILEMCP_DISABLE_TELEMETRY=1.

  2. LowHTTP server mode accepts unauthenticated connections when MOBILEMCP_AUTH is unset

    src/index.ts:37

    When started with --listen, the server logs a warning and accepts unauthenticated MCP requests unless the MOBILEMCP_AUTH environment variable is set. If bound to 0.0.0.0 or a LAN interface (as shown in the README), anyone on the network—and websites via DNS rebinding, because Host-header protection is only enabled for loopback addresses—can control connected phones, capture screenshots, read clipboards and logs, or manage cloud devices without an AI involved; additionally, when MOBILEMCP_AUTH is set, the Bearer token check uses non-constant-time !== string comparison.

    Fix: Refuse to start --listen on non-loopback addresses unless MOBILEMCP_AUTH is set (or require MOBILEMCP_AUTH for all --listen binds unless explicitly opted out), and compare Bearer tokens with crypto.timingSafeEqual.

  3. LowMissing package name validation in mobile_uninstall_app allows flag and legacy adb shell injection

    src/android.ts:393

    Unlike launchApp and terminateApp in the same file, AndroidRobot.uninstallApp does not call validatePackageName before invoking adb uninstall, and the default MobileDevice app methods also pass packageName directly to mobilecli without validation. If prompt injection tricks the agent into calling mobile_uninstall_app with flags (such as -k) or shell metacharacters while MOBILEMCP_LEGACY_ROBOT=1 is enabled, adb forwards the unvalidated argument into the Android device's package-manager shell command, allowing unintended flags or arbitrary adb shell commands on the connected Android device.

    Fix: Call validatePackageName(packageName) in src/server.ts across mobile_launch_app, mobile_terminate_app, mobile_uninstall_app, and mobile_clear_app_data so every robot backend rejects CLI flags and shell metacharacters.

  4. LowPlugin manifests and installer run unpinned @latest package from npm at startup

    plugin/.claude-plugin/plugin.json:17

    The Claude Code plugin manifest, mcp.json, and the mobile-mcp install command configure clients to execute npx -y @mobilenext/mobile-mcp@latest. Because -y skips confirmation and @latest is unpinned, every new agent session downloads and executes whatever version is currently tagged latest on npm, exposing users to immediate host code execution if the npm package or publisher account is ever compromised.

    Fix: Pin @mobilenext/mobile-mcp to an exact version matching the installed plugin or CLI release instead of using @latest.

  5. LowPredictable /tmp paths in /mobile-mirror collide across users and leave screenshots on disk

    plugin/hooks/register.tsx:44

    The /mobile-mirror Claude Code command writes live device screenshots to fixed paths (/tmp/mobile-mirror-0.png through /tmp/mobile-mirror-2.png) in the shared world-writable /tmp directory and never deletes them when the pane closes. On multi-user machines, another local user can pre-create those filenames in sticky /tmp to block mirroring, concurrent sessions overwrite each other's frames, and if a pre-existing user-owned file had broader permissions, writeOutputFile preserves that mode.

    Fix: Create a private 0700 temporary directory per mirror session (similar to createPrivateOutputPath in src/utils.ts) and remove it when the mirror pane closes.