devicefarm

This MCP server exposes AWS Device Farm remote access sessions and mobile automation through Appium. It integrates with AWS Device Farm to manage real devices in the cloud and provides an MCP-compatible interface for AI assistants and automation clients to create sessions, manage devices, and run Appium/WebDriver commands over secure endpoints. Core capabilities include creating remote access sessions, listing devices, and performing common mobile automation tasks such as taking screenshots, simulating gestures, typing text, launching and terminating apps, and querying device information. The server handles APK/app installation when needed and automatically coordinates with Device Farm to expose a managed Appium endpoint for test automation. To use it, run the MCP server in your environment (via npx, npm, or from source) and configure your MCP client to point at the devicefarm server name, providing necessary AWS credentials and the Device Farm project ARN. Once running, you can issue commands like create_session, mobile_get_screen_size, mobile_click_on_screen_at_coordinates, mobile_type_keys, mobile_launch_app, and more, all routed through the MCP protocol to AWS Device Farm.

Prerequisites:

• Node.js v18 or higher
• npm (comes with Node.js)
• AWS credentials with permissions for Device Farm (see README prerequisites)

Installation steps:

1. Quick start (no local install required):

npx devicefarm-mcp-server

2. Install globally (optional):

npm install -g devicefarm-mcp-server
devicefarm-mcp-server

3. From source (if you prefer to run from repo):

git clone https://github.com/yoreland/devicefarm-mcp-server.git
cd devicefarm-mcp-server
npm install
node devicefarm-mcp-server.js

Prerequisites and configuration notes are detailed in the README, including setting DEVICEFARM_PROJECT_ARN and AWS credentials, which are required for the MCP server to operate with AWS Device Farm.

Tips and considerations:

• Ensure AWS credentials are configured in one of the supported ways (environment variables, AWS CLI config, or AWS profile) and that DEVICEFARM_PROJECT_ARN is set.
• The MCP client configuration should pass through AWS region and credentials to the server via environment variables.
• The server maintains a single active session by design and handles automatic Appium driver initialization when a session starts.
• If you encounter permission errors, verify that your IAM user/role has the following Device Farm actions: CreateRemoteAccessSession, GetRemoteAccessSession, StopRemoteAccessSession, ListDevices, CreateUpload, GetUpload, InstallToRemoteAccessSession.
• Use the provided Appium endpoint through the WebDriver/W3C protocol for driving automation; Device Farm handles the Appium server in the cloud, so there is no local Appium setup required.
• When using APK/App installation workflows, provide apkPath or appArn as needed; the server will upload, process, and install the app on the remote device as part of session creation.