Ext Ops Panel
Open dashboard
Comparison

Mobilerun vs UIAutomator2 MCP Server

Mobilerun is an MCP server published by droidrun. Marketplaces we read that list it: 1 (Official MCP Registry). UIAutomator2 MCP Server is an MCP server published by tanbro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceMobilerunUIAutomator2 MCP Server
Official MCP Registry Listed
Version: 1.1.0
Forks (GitHub): 1 044
Stars (GitHub): 9 827
Not marked · First seen
Listed
Version: 0.3.3
Downloads/month (PyPI): 314
Downloads/week (PyPI): 380
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Mobilerun vs UIAutomator2 MCP Server
FactMobilerunUIAutomator2 MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)9 827No figure on GitHub
Forks (GitHub) (differs)1 044No figure on GitHub
Last release (differs)2026-10-27Not published
Where it runs (differs)Remote server (cloud.mobilerun.ai/api/mcp)On your machine (uiautomator2-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/droidrun/mobilerun-mcpNot stated
Changes in the last 7 days (differs)50
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Mobilerun

In its own words, on Official MCP Registry:

Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.

UIAutomator2 MCP Server

In its own words, on Official MCP Registry:

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

How to run each

Mobilerun As a remote MCP server

Claude Code
claude mcp add --transport http mobilerun https://cloud.mobilerun.ai/api/mcp

UIAutomator2 MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio uiautomator2-mcp-server -- uvx uiautomator2-mcp-server stdio

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Mobilerun · What it can do: UIAutomator2 MCP Server · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built