Mobdev vs Mobilerun
A side-by-side look at the Mobdev 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 Mobdev for os automation work; 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 Mobdev when
- You need dedicated capabilities in the OS Automation domain.
- 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 | 36/100 · Fair | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | 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 | 0 | 9,709 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Mobdev | View Mobilerun |
Tools & capabilities
Mobdev 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.
Mobdev
No confirmed install command for Mobdev yet — follow the setup steps linked from its listing page rather than a guessed package name.
Mobilerun
{
"mcpServers": {
"mobilerun": {
"command": "uvx",
"args": [
"mobilerun"
]
}
}
}
Frequently asked questions
Mobdev is categorized under OS Automation and uses an install path we have not confirmed yet. Mobilerun belongs to OS Automation and uses a local stdio subprocess. Pick Mobdev 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. Mobdev has no confirmed install command yet — follow its own setup instructions.
Mobdev 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 mobdev and mobilerun as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mobdev has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Mobilerun has 48/100 (Fair) with 1 views, 0 installs and 9,709 GitHub stars.