← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionMobile MCPCross-platform mobile automation and development for iOS, Android, simulators, emulators, and real devicesMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS39 / 100 · D79 / 100 · B
Reliability3 / 2012 / 20
Security and permissions5 / 2018 / 20
Maintenance8 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • Developers or test teams needing unified API across iOS and Android
  • Those looking to reduce dependency on platform-specific knowledge like XCUITest or Espresso
  • Scenarios requiring structured, deterministic output (accessibility tree based) rather than screenshot-only
  • Automation on local or cloud emulators/simulators
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Use cases requiring visual understanding (e.g., image recognition) or complex image verification (server is accessibility-first, using screenshots only when needed)
  • General desktop automation without mobile device interaction
  • Teams requiring official support or enterprise guarantees (third-party open-source project)
  • Environments unable to meet prerequisites (Xcode, Android SDK, Node.js v20+)
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Access to local filesystem to install apps and save screenshots/videos
  • Network access to install npm packages and possibly cloud services
  • USB debugging permissions or go-ios/WebDriverAgent setup for real devices
  • Port availability and optional auth token for SSE mode
  • May send anonymous usage telemetry (can be disabled via environment variable)
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Automated mobile actions may cause unintended operations or data loss (e.g., sending messages, purchases)
  • Credentials provided (e.g., email) could be stored or misused
  • URL opening feature may be used to open non-standard schemes (blocked by default, requires explicit allow)
  • SSE server without authorization may be accessed by unauthorized parties
  • Dependency on unstable third-party tools (e.g., go-ios, WebDriverAgent)
  • Telemetry may include sensitive usage patterns
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, Claude Code, Codex, Gemini CLI, GitHub Copilot, Cursor, Windsurf, Amp, Antigravity 2, Cline, Goose, Kiro, OpenCodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools230