mcp-mobile

Automate mobile app testing by using deterministic MCP tool commands to drive device interaction workflows. You can discover devices, launch apps by package name, and run UI flows including taps, swipes, typing, and orientation changes across iOS and Android environments.

Element discovery for mobile UI testing works by inspecting on-screen element trees and extracting coordinates. The mobile_list_elements_on_screen command queries the active screen layout, enabling automated taps and swipes on specific UI components.

Yes, you can capture screenshots and validate UI behavior during automated mobile testing. The mobile_take_screenshot command records the current screen state, which is essential for reproducible bug reproduction and end-to-end UI testing validation.

Before running automated swipe and tap workflows, you need available iOS simulators or Android emulators and the target app's package name. The mobile_list_available_devices command verifies connected device states and readiness before app launch and interaction.

Yes, programmatic orientation changes are supported during mobile emulator testing. The mobile_set_orientation command alters the device screen layout, allowing you to validate responsive UI behavior and reproduce orientation-specific bugs within automated testing workflows.

MCP patterns for mobile device interaction apply deterministic command sets suited for reproducible UI tasks. They are limited to iOS simulators and Android emulators, meaning physical hardware device testing and real sensor interaction workflows are outside the supported scope.