Ross ROSS = Recommend OSS · open-source software intelligence for agents

mobile-next/mobile-mcp

Model Context Protocol Server for Mobile Automation and Scraping (iOS, Android, Emulators, Simulators and Real Devices) observed · 2026-08-28

github.com/mobile-next/mobile-mcp · homepage · TypeScript · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

86/100

  • Activity 99
  • Release rhythm 96
  • Longevity 37
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: 5
  • age_days: 523
  • days_rel: 24
  • days_push: 7
  • n_releases_24m: 52

Full methodology

Adoption not part of the score

6033 stars · 515 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

An open-source Model Context Protocol (MCP) server that lets AI agents and LLMs control iOS and Android devices—emulators, simulators, and real hardware—through accessibility snapshots and screenshot-based interactions. It is part of the Mobile Next ecosystem alongside a CLI, a Playwright-style framework, and a paid cloud device farm.

Use cases

  • automate native iOS and Android app testing with an AI agent
  • let Claude or Cursor tap and swipe on a real phone via MCP
  • extract data from mobile apps without manual device control
  • run multi-step user journeys on simulators and emulators driven by an LLM
  • script form filling and data entry on mobile devices
  • give coding agents device access to verify app changes with screenshots

When to choose

  • you want an MCP-compatible agent to drive local iOS/Android devices without platform-specific glue
  • you need accessibility-tree-based automation that avoids vision-model token costs
  • you want one interface across emulators, simulators, and real devices
  • you are building agent workflows that include mobile app interaction or scraping

When to avoid

  • you need a traditional scripted test framework without an LLM agent (consider Appium or the companion Mobilewright)
  • you only target web browsers rather than native mobile apps
  • you require guaranteed SLA support from the open-source project alone
  • your environment cannot run Node.js or connect to physical/virtual devices

Facets

service · maturity active

mcp agent-framework testing workflow-automation web-scraping mobile-development testing developer-tools cli cross-platform mcp-server mobile-automation device-farm llm-agents appium-alternative accessibility-tree simulator emulator real-devices ai-agents automation android ios nodejs

4 sources

Member repositories

RepositoryRoleHealth v2
mobile-next/mobile-mcpmain86

For agents

markdown · JSON · MCP: product_card(name="mobile-next/mobile-mcp")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem