MCP Appium - Mobile Development and Automation Server

io.github.ihubanovPublished by GitHub account ihubanovv1.33.1Updated Nov 7, 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.ihubanov/squire
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Nov 3, 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 ihubanov 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.ihubanov%2Fsquire.svg)](https://sourceweft.com/mcp/io.github.ihubanov%2Fsquire?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 and creating mobile tests.

What you can do: Drive Appium sessions on iOS and Android devices
Interact with mobile app interfaces during automated runs
Create and manage mobile test cases
Support mobile development and QA workflows
When to use it: Useful when you want an assistant to help script, run or maintain Appium-based mobile UI automation and test creation for iOS and Android apps.
Requirements: Runs as a local stdio process installed from the npm package @sniffski/squire, so Node.js and npm are needed. Appium and reachable iOS or Android devices or emulators are implied by the purpose but not documented here. No authentication, environment variables or headers are declared.

Before you install

It drives real devices and emulators, so automated actions can change app state or data on those devices. No tool list, README or instructions were provided, so the exact commands and permissions it exposes are unverified.

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 has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.33.1LatestNov 7, 2026
v1.31.6Nov 3, 2026
v1.31.5Nov 3, 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.