UIAutomator2 MCP Server

io.github.tanbroPublished by GitHub account tanbrov0.3.3Updated Oct 24, 2026

Android mobile automation with uiautomator2. AI bot for taps, swipes, apps, XPath testing, RPA.

VerifiedSTDIODesktop onlyBrowser Automation Developer Tools

Server details

Identifier: io.github.tanbro/uiautomator2-mcp-server
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 tanbro 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.tanbro%2Fuiautomator2-mcp-server.svg)](https://sourceweft.com/mcp/io.github.tanbro%2Fuiautomator2-mcp-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an AI assistant drive an Android device through uiautomator2 for taps, swipes, app control, XPath testing and RPA.

What you can do: Control the device with taps and swipes and other UI gestures via uiautomator2 automation commands. Launch and manage Android apps on the connected device. Test and evaluate XPath selectors against the device UI. Support RPA-style repetitive mobile workflows driven by the assistant.
When to use it: Use it when you want an assistant to operate or test an Android device hands-on, such as running repetitive UI flows, checking XPath selectors, or automating app interactions from a desktop session.
Requirements: Runs as a local process on the user's machine, installed from the PyPI package uiautomator2-mcp-server over stdio. Requires Python and an Android device reachable from that machine, with uiautomator2 set up on the device. Desktop only; no web executable. No authentication, environment variables or headers are declared.

Before you install

The server can act on a real Android device, performing taps, swipes and app actions that change device state; review what it will do before letting it run unattended. It is desktop-only and needs a connected device, so scope it to a test or dedicated device where possible.

Installation

In SourceWeft

Open UIAutomator2 MCP 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

v0.3.3LatestSep 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.