Appium MCP: What It Is, How to Set It Up, and Where It Stops (2026)

Appium MCP is a Model Context Protocol server that lets an AI assistant such as Cursor, Claude Code or Gemini CLI drive Android and iOS devices through Appium. You describe what you want in the chat, and the assistant starts the session, inspects the screen and performs the steps by calling Appium for you.

This guide covers what Appium MCP is, which of the several projects with that name people usually mean, how to set it up, what it is good for, and where it stops. If you need the basics of Appium itself first, start with what Appium is and how its architecture works.

What is Appium MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools. An MCP server exposes a set of tools, and the assistant decides when to call them while it works on your request.

An Appium MCP server exposes Appium automation as those tools. The assistant can start a session on a device, find elements, tap and type, and generate locators and test code from what it sees.

The official implementation is MCP Appium, maintained under the Appium project at appium/appium-mcp and published on npm as appium-mcp. It describes itself as an MCP server for mobile development and automation across iOS, Android, simulators, emulators and real devices.

Which "Appium MCP" do you mean?

Several projects share the name, which makes search results confusing. These are the ones you are most likely to run into.

Note that appium-mcp on npm and appium-mcp on PyPI are different projects from different maintainers.

How to set up Appium MCP

Prerequisites

• Node.js 22 or later
• Java (JDK 8 or later)
• For Android: the Android SDK, with ANDROID_HOME set
• For iOS: macOS with Xcode
• An MCP-compatible client

Add the server to your client

Cursor: go to Cursor Settings, then MCP, then Add new MCP Server, and use the command npx -y appium-mcp@latest.

Claude Code:

claude mcp add appium-mcp -- npx -y appium-mcp@latest

Gemini CLI:

gemini mcp add appium-mcp npx -y appium-mcp@latest

Any other MCP client that reads a JSON config:

{
  "mcpServers": {
    "appium-mcp": {
      "command": "npx",
      "args": ["appium-mcp@latest"],
      "env": {
        "ANDROID_HOME": "/path/to/Android/sdk"
      }
    }
  }
}

Choose how it connects to devices

MCP Appium supports two driver modes.

• Embedded local drivers. When you create an Android or iOS session without a remote server URL, it uses its bundled UiAutomator2 or XCUITest driver directly. You do not need to start a separate Appium server for local work.
• Remote Appium server. Pass a remoteServerUrl when creating or attaching to a session and it connects to an Appium server you already run instead. This mode is also required for platforms other than Android and iOS.

Run a first prompt

With an emulator or simulator running, ask the assistant something like:

Start an Android session on the running emulator, open the app, and tap Login. Then list the elements on the next screen.

The project is moving quickly, so check the README in the repository for the current tool list and options before you rely on any one of them.

What Appium MCP is good for

• Exploring an app and getting a first draft of a test. The assistant can walk a flow and write the script as it goes.
• Generating locators without clicking through a GUI. It can propose locators for the elements on screen, which is the job Appium Inspector does by hand.
• Debugging a failing step. You can ask it to reproduce the step on a device and report what is on screen.
• Keeping developers in their editor. A developer can drive a device from the same tool they write code in.

Where Appium MCP stops

• It is still Appium underneath. It uses the same drivers and has the same setup requirements: the Android SDK for Android, a Mac with Xcode for iOS, and a device or emulator to run on.
• The tests it writes are still locator-based. When a developer renames an ID or restructures a screen, those locators break the same way they always have. MCP changes who writes the locator. It does not remove it.
• An assistant in the loop is slower and less predictable than a script. Each step involves a model deciding what to do. That is fine for authoring and debugging. It is not what you want running your regression suite in CI.
• The ecosystem is young. There are several competing implementations and the tool lists are still changing.

Appium MCP vs AI-native mobile testing

These are two different uses of AI.

Appium MCP puts an AI assistant in front of Appium. The assistant writes and operates selector-based automation faster than a person would, but the result is still selector-based automation.

AI-native tools such as Drizz replace the selector layer. Tests are written in plain English and Vision AI finds each element on the rendered screen, so there is no locator to maintain when the UI changes.

Which one helps depends on where your time goes. If the bottleneck is writing Appium tests, Appium MCP will speed that up. If the bottleneck is maintaining them, it will not change much, and it is worth comparing the best Appium alternatives or reading Drizz vs Appium.

FAQ

What is an Appium MCP server?

It is a Model Context Protocol server that exposes Appium's mobile automation as tools an AI assistant can call. It lets the assistant start device sessions, find and interact with elements, and generate locators and test code.

Is Appium MCP official?

Yes. MCP Appium, published on npm as appium-mcp, is maintained under the Appium project. Several community projects use similar names, so check the maintainer and package registry before installing.

Do I need a running Appium server to use it?

Not for local sessions with the official server. It bundles the UiAutomator2 and XCUITest drivers and uses them directly. Some community servers do require you to start Appium yourself.

Does Appium MCP remove the need for locators?

No. It can generate locators for you, but the tests still depend on them and still break when the underlying identifiers change.

Which AI clients work with Appium MCP?

Any MCP-compatible client. The project documents setup for Cursor, Claude Code and Gemini CLI.