AutoMobile

dev.jasonpearsonPublished by jasonpearson.devv0.0.67Updated Oct 24, 2026

Mobile device interaction automation via MCP

VerifiedSTDIODesktop onlyBrowser Automation Developer Tools

Server details

Identifier: dev.jasonpearson/auto-mobile
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 that this server's namespace belongs to jasonpearson.dev. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

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/dev.jasonpearson%2Fauto-mobile.svg)](https://sourceweft.com/mcp/dev.jasonpearson%2Fauto-mobile?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

AutoMobile lets an AI assistant drive Android and iOS devices in natural language to explore app UX, reproduce bugs and run UI tests.

What you can do: Observe and inspect app screens quickly through platform accessibility and test services
Tap, swipe, pinch, drag and drop, and shake with automatic element targeting
Explore app UX, map screens and user flows, and identify confusing interactions
Reproduce bugs from a bug report with exact steps and screenshots
Create and execute UI tests from plain-English scenarios, including multi-device runs
Profile cold and warm startup time and detect scroll jank
When to use it: Useful for mobile engineers and QA who want an assistant to navigate real Android or iOS apps, turn bug reports into reproduction steps, generate and run UI tests, or measure launch and scroll performance.
Requirements: Runs as a local stdio process on a desktop machine, launched with bunx from the npm package. Needs host platform tooling such as adb for Android and simctl/Xcode tooling for iOS, plus connected devices or simulators; an interactive installer and a Homebrew CLI are offered. No authentication, environment variables or headers are declared.

Before you install

The assistant can inject touches and run tests on real devices or simulators, so it can change app state and data. The documented installer is a shell script fetched from the internet and run directly, and it may download Android or iOS developer tools; review it before running. Desktop only, with no web executable.

Installation

In SourceWeft

Open AutoMobile 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.

Other MCP clients

Follow the launch instructions in the repository.

README

AutoMobile

[Pull Request] [On Merge] [Nightly] [License]

[Platform: macOS] [Platform: Linux]

[TypeScript tests] [Kotlin tests] [Swift tests] [Kotlin coverage] [Swift coverage]

[AutoMobile sticker]

AutoMobile lets AI agents control your mobile devices using natural language. Tell an AI what you want to do, and it interacts with your Android or iOS app.

It can do all this by being an MCP server that uses standard platform tools like adb & simctl paired with additional Kotlin & Swift libraries and apps. All components are open source. The point is to provide mobile engineers with AI workflow tools to perform UX deep dives, reproduce bugs, and run automated tests.

[Setting an alarm in the Clock app] An AI agent navigating to the Clock app, creating a new alarm

[Searching YouTube for a video] An AI agent searching YouTube and browsing results

Explore and Test

Task	What it does
Explore app UX	Navigate your app, discover screens, map user flows, identify confusing interactions
Reproduce bugs	Paste a bug report and get exact reproduction steps with screenshots
Create UI tests	Describe test scenarios in plain English, get executable test plans
Measure startup time	Profile cold and warm launch performance
Check scroll performance	Detect jank and dropped frames

How it works

🤖 Fast UX Inspection Kotlin Accessibility Service and Swift XCTestService to enable fast, accurate observations. 10x faster than the next fastest observation toolkit.
🦾 Full Touch Injection Tap, Swipe, Pinch, Drag & Drop, Shake with automatic element targeting.
♻️ Tool Feedback Observations drive the interaction loop for all tool calls.
🧪 Test Execution Kotlin JUnitRunner & Swift XCTestRunner execute tests natively handling device pooling, multi-device tests, and automatically optimizing test timing.

Get Started

You can use our interactive installer to step through all host platform requirements and configuration options. It checks host dependencies, optionally downloads Android or iOS developer tools, and configured the MCP daemon.

bash

curl -fsSL https://raw.githubusercontent.com/kaeawc/auto-mobile/refs/heads/main/scripts/install.sh | bash

curl -fsSL https://raw.githubusercontent.com/kaeawc/auto-mobile/refs/heads/main/scripts/install.sh | bash

Prefer Homebrew for the CLI:

or follow the installation guide.

Documentation

Full Documentation - Complete guide with examples
FAQ - Common questions answered
Design Docs - Architecture and implementation details

Contributing

Code of Conduct
Security policy - report vulnerabilities privately via GitHub
Contributing

Source: README.md at commit 43b68da

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.0.67LatestSep 16, 2026

Score

50% 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
License10 pts