Tools/mobile-next/mobile-mcp

mobile-mcp

MCP server for iOS and Android device automation via accessibility APIs

9.1k ★+380/wkemergingTypeScriptApache-2.0trending

The Lens

By Erik Loyd, SaaS CEO and former COO/CFO of an AWS Premier Partner.

Updated Sep 2026

MCP server for automating iOS and Android devices. Your AI assistant taps buttons, reads screen content, takes screenshots and navigates apps through native accessibility APIs rather than computer vision, which is why it is fast and does not break when a button moves two pixels.

Needs Node.js 22+, plus Xcode for iOS or the Android SDK. One npm install, then point your MCP client at it. Works against emulators, simulators and real devices wired to your machine. Maintained by Mobile Next, a commercial company, not a community project, and the server itself is Apache 2.0.

Free and the best option for driving mobile apps from an assistant. The catch is what sits next to it: Mobile Next also sells a paid cloud for real-device sessions billed per device-minute, and their Mobile CLI ships under the Functional Source License rather than Apache. The MCP server is genuinely open; the surrounding toolchain is not uniformly so.

Free vs Self-Hosted vs Paid

fully free

Free (Open Source)

  • Apache 2.0 MCP server, installed with a single npm command
  • Native accessibility APIs for tapping, reading screen content, screenshots and navigation
  • Works with iOS simulators, Android emulators and real devices attached to your machine
  • No account, no auth token, no usage cap on locally attached devices
  • Requires Node.js 22+, plus Xcode for iOS or the Android SDK

Paid

  • Mobile Next Cloud for real-device infrastructure: start a session over the API, connect via MCP or the CLI, and pay per device-minute. Free to try; per-minute rates are published on their pricing page rather than here
  • Note the licensing split: mobile-mcp and Mobilewright are Apache 2.0, but Mobile CLI ships under the Functional Source License, which is source-available rather than open source

Self-Hosted Costs

$0 to run the server. The real cost is device coverage. Simulators and emulators are free but do not catch hardware-specific bugs; a physical device farm means buying and maintaining handsets, which is exactly the problem the paid cloud sells against.

When to Pay

Pay for the cloud when you need real devices you do not own, across OS versions and form factors, and per-device-minute billing beats buying and racking handsets. For local development against a simulator or the phone on your desk, the free server is the whole product.

The MCP server is free and Apache 2.0. Mobile Next sells a paid cloud for real-device sessions billed per device-minute, and their separate Mobile CLI is source-available under the FSL rather than open source.

What to do by team size

Solo
free; a simulator and the phone on your desk cost nothing
Small team
free for local devices; the cloud only when you need hardware you do not own
Medium team
free server plus paid cloud device-minutes for cross-device coverage
Large team
free server; price the cloud against maintaining your own device farm
Self-hosting ops:moderate
View pricing page →

Get tools like this every Wednesday

One featured tool, three on the radar. No fluff.

Score
80/100 · A
Adoption21/30
Maintenance25/25
Community9/20
License15/15
Analysis10/10

A low score is not a verdict on quality. Young and niche tools start low by design. How we calculate scores

Trust Signals

Community discussions enabledOrganization account (17 public repos)

About

Owner
mobile-next (Organization)
Stars
9,112
Forks
817

Explore Further

More tools in the directory