MCP Appium - Mobile Development and Automation Server

io.github.appiumPublished by GitHub account appiumv1.99.3Updated Nov 4, 2026

MCP server for Appium mobile automation on iOS and Android devices with test creation tools.

VerifiedSTDIODesktop onlyBrowser Automation Developer Tools

Server details

Identifier: io.github.appium/appium-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account appium for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.appium%2Fappium-mcp.svg)](https://sourceweft.com/mcp/io.github.appium%2Fappium-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that connects an assistant to Appium for automating iOS and Android devices, including creating mobile tests.

What you can do: Drive Appium sessions against iOS and Android devices and apps.
Inspect and interact with mobile UI elements during automation runs.
Create and work with mobile test scripts through the assistant.
Run as a local stdio process on the user's desktop machine.
When to use it: Useful when you want an assistant to help write or run Appium-based mobile automation and tests for iOS or Android apps, and you already work with Appium locally.
Requirements: Runs as a local npm package (appium-mcp) over stdio on a desktop machine. No authentication, environment variables or headers are declared. Appium itself and connected devices or emulators are implied by the purpose but not specified in the listing.

Before you install

The server can drive real devices and apps, so automation actions may change app state or data. No credentials are declared, but device access and any Appium server configuration are under your control. Desktop only; no web executable.

Installation

In SourceWeft

Open MCP Appium - Mobile Development and Automation Server in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not answer in time.

Version history

v1.99.3LatestNov 4, 2026
v1.99.2Nov 1, 2026
v1.99.1Oct 29, 2026
v1.99.0Oct 26, 2026
v1.98.0Oct 26, 2026
v1.97.1Oct 12, 2026
v1.97.0Oct 12, 2026
v1.94.0Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.