Agent Device vs Mobile Device MCP
A side-by-side look at the Agent Device and Mobile Device MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Device for os automation work; choose Mobile Device MCP 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 Agent Device when
- You need dedicated capabilities in the OS Automation domain.
- Its auth model fits you: No auth required.
Choose Mobile Device MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_devices, screenshot, uitree.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 52/100 · Good | 59/100 · Good |
| 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 | 5,125 | 52 |
| Directory activity | 3 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 14 |
| Full listing | View Agent Device | View Mobile Device MCP |
Tools & capabilities
Agent Device tools
No tool names declared yet. Check the project README from the listing page.
Mobile Device MCP tools 14
list_devicesList available iOS and Android devicesscreenshotCapture the device screen (JPEG)uitreeGet the UI element tree as a flat list, with optional search and limit. Off-screen elements are excluded unless `include_invisible: truetapTap at screen coordinatesdouble_tapDouble-tap at screen coordinateslong_pressLong-press at screen coordinates (configurable duration)scrollSwipe from start to end coordinatestype_textType text into the focused elementpress_buttonPress a hardware/navigation button (home, back, enter, volumeUp/Down, dpadUp/Down/Left/Right/Center)launch_appLaunch an app by bundle ID / package nameterminate_appForce-stop an applist_appsList installed apps- +2 more on 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.
Agent Device
No confirmed install command for Agent Device yet — follow the setup steps linked from its listing page rather than a guessed package name.
Mobile Device MCP
{
"mcpServers": {
"mobile-device-mcp": {
"command": "npx",
"args": [
"-y",
"@srmorete/mobile-device-mcp@latest"
]
}
}
}
Frequently asked questions
Agent Device is categorized under OS Automation and uses an install path we have not confirmed yet. Mobile Device MCP belongs to OS Automation and uses a local stdio subprocess. Pick Agent Device for os automation work and Mobile Device MCP 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. Agent Device has no confirmed install command yet — follow its own setup instructions.
Agent Device is listed as free. Auth: no auth required. Mobile Device MCP 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 callstackincubator-agent-device and mobile-device-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Device has a quality signal of 52/100 (Good) with 3 views, 0 installs and 5,125 GitHub stars. Mobile Device MCP has 59/100 (Good) with 4 views, 0 installs and 52 GitHub stars.