mcp-appium

This MCP server package provides an Appium-based WebdriverIO test automation workflow for validating a sample mobile app across Android and iOS. It exposes a ready-to-run test suite that demonstrates a Page Object Model structure, supporting Android E2E form interactions and iOS swipe functionality using Appium. The server leverages WebdriverIO configurations (wdio.conf.ts and platform-specific confs) to orchestrate test runs, collect results, and provide consistent run commands for Android and iOS environments. You can use it to quickly verify mobile app automation pipelines or extend it with additional test specs and page objects as needed.

When you start the server via MCP, you gain access to: - Android Forms E2E tests that validate text input, switch toggling, dropdown selection, and dialog interactions. - iOS Swipe E2E tests that exercise a carousel, extract card descriptions, and verify content across multiple cards. - Predefined Run commands for individual suites and all tests, using the appropriate WebdriverIO configuration files.

Prerequisites:

• Node.js v18 or higher
• npm or yarn
• Access to install Appium globally (npm install -g appium) if you intend to run tests locally
• Android SDK and an emulator running, or iOS Simulator/macOS with Xcode installed

Installation steps:

1. Install Node.js dependencies via npm:

npm install

2. Ensure Appium is installed globally (optional if included in package scripts):

npm install -g appium

3. Run the MCP server package (from your project root or where MCP is configured):

npx -y arkhangelsk-mcp-appium-server

4. If you maintain a local environment, you may also install via npm directly in development:

npm install arkhangelsk-mcp-appium-server

5. Verify that the WebdriverIO configurations and test suite are accessible and that Android/iOS emulators are running or simulators are available before executing tests.

Tips and notes:

• The Android tests target the app with package name com.wdiodemoapp and assume an Android Emulator is running. Ensure the emulator is ready before starting tests.
• The iOS tests rely on the app bundle located at app/ios/wdio.zip and require a macOS environment with Xcode Command Line Tools installed. Increase installation timeouts if the ZIP extraction is slow.
• If you encounter element not found errors, verify selectors in the Page Object Model files under test/pageobjects.
• The tests use the W3C Actions API for iOS gestures; avoid deprecated touchPerform for compatibility.
• You can customize timeouts in wdio.conf.ts and platform-specific configs (e.g., newCommandTimeout, connectionRetryTimeout).
• Ensure environment variables for device/simulator configuration are set if you adapt the setup to different platforms or CI environments.