AutoMobile vs Mobilerun
A side-by-side look at the AutoMobile and Mobilerun MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AutoMobile for os automation work as a local process; choose Mobilerun for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AutoMobile when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Mobilerun when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 49/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 52 | 9,709 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View AutoMobile | View Mobilerun |
Tools & capabilities
AutoMobile tools
No tool names declared yet. Check the project README from the listing page.
Mobilerun tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AutoMobile
{
"mcpServers": {
"automobile": {
"command": "npx",
"args": [
"-y",
"@kaeawc/auto-mobile"
]
}
}
}
Mobilerun
{
"mcpServers": {
"mobilerun": {
"command": "uvx",
"args": [
"mobilerun"
]
}
}
}
Frequently asked questions
AutoMobile is categorized under OS Automation and uses a local stdio subprocess. Mobilerun belongs to OS Automation and uses a local stdio subprocess. Pick AutoMobile for os automation work and Mobilerun for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AutoMobile is listed as free. Auth: no auth required. Mobilerun has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add automobile and mobilerun as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AutoMobile has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 52 GitHub stars. Mobilerun has 48/100 (Fair) with 1 views, 0 installs and 9,709 GitHub stars.