AutoMobile
Drive real iOS or Android devices from your agent via MCP when building or regression-testing mobile apps.
Overview
dev.jasonpearson/auto-mobile is an MCP server for the Build phase that automates mobile device interactions for agent-driven development and testing.
What is this MCP server?
- AutoMobile MCP server (dev.jasonpearson/auto-mobile) for mobile interaction automation
- stdio transport via npx @kaeawc/auto-mobile (runtimeHint npx, npm 0.0.13)
- Open-source package from github.com/kaeawc/auto-mobile
- Documentation site at kaeawc.github.io/auto-mobile
- npm package @kaeawc/auto-mobile version 0.0.13
- stdio MCP transport via npx runtimeHint
- GitHub source: kaeawc/auto-mobile
Community signal: 36 GitHub stars.
What problem does it solve?
Mobile debugging stalls when your agent can edit code but cannot reliably drive the device under test.
Who is it for?
Solo builders shipping React Native, Flutter, or native apps who want MCP-native device automation via npx.
Skip if: Pure backend or web-only projects with no on-device validation needs.
What do I get? / Deliverables
Your agent can run scripted device interactions through MCP while you iterate on UI and flows on real hardware.
- Agent-triggered mobile UI flows on connected devices
- Repeatable smoke paths without rewriting ad-hoc automation each sprint
- Local stdio MCP wiring documented in your project MCP config
Recommended MCP Servers
Journey fit
Device automation belongs in the build phase where you wire agent tooling into how the app is exercised on hardware. agent-tooling is the shelf for MCP servers that extend the coding agent with device control rather than app business logic.
How it compares
Device-control MCP integration, not a hosted mobile CI farm or Appium skill pack.
Common Questions / FAQ
Who is dev.jasonpearson/auto-mobile for?
Developers building mobile apps with AI coding agents who need programmatic device taps, navigation, and checks from the same session as code edits.
When should I use dev.jasonpearson/auto-mobile?
Use it during build and pre-ship smoke testing when you want the agent to exercise flows on a connected phone or emulator through MCP.
How do I add dev.jasonpearson/auto-mobile to my agent?
Add the npm MCP server @kaeawc/auto-mobile with stdio transport and runtimeHint npx in your Claude Code or Cursor MCP config, following the AutoMobile docs site.