Mobile MCP Server

Purpose

The Mobile MCP Server gives you full control over real iOS and Android devices hosted in Mobitru.
It is designed for test automation, device management, and advanced debugging through AI assistants such as Copilot, Cursor, or EliteA.

Primary Use Cases

  • Reservation and lifecycle management of real devices (iOS / Android).
  • App upload, installation, resigning, and injection.
  • Appium session control for both automated and manual tests.
  • Device-level interactions — open URLs, tap, swipe, type, rotate screen.
  • Environment configuration — network throttling, GPS coordinates, IP overrides.
  • Capturing logs, video recordings, performance traces, and HTTP traffic.
  • Integration with testing frameworks such as Espresso, XCUITest, and Appium.

Typical Workflow

StepDescription
1. Check farmList available devices and their statuses (online, busy, offline).
2. Reserve deviceReserve a specific device by OS, version, or serial number.
3. Select deviceActivate the reserved device in context for subsequent actions.
4. Initialize AppiumCreate an Appium session linked to the current device.
5. Execute actionsInstall and launch apps, perform UI actions, capture logs or screenshots.
6. Close AppiumGracefully terminate the Appium session once testing is done.
7. Release deviceFree the device back to the pool for other users.

Example Flow

List all available iOS devices
Reserve iPhone 15 for 180 minutes
Install demo_app.ipa with resign
Launch the app and open the settings page
Take a screenshot
Close Appium session and release device

Notes:

  • The Mobile MCP server communicates with Mobitru via secure HTTPS endpoints.
  • App resigning uses the Mobitru enterprise provisioning profile.
  • The same Appium session can control multiple apps within one reserved device context.
  • You can have multiple active Mobile MCP sessions in parallel.
Scroll to Top