Mobilerun vs Agent Device

A side-by-side look at the Mobilerun and Agent Device MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Mobilerun logoMobilerunOS Automation · Local subprocess (stdio)Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.48FairAuth: not declaredAgent Device logoAgent DeviceOS AutomationDiscovery router for the agent-device CLI. Exposes status, install guidance, version-matched help, prompts, and resources for iOS, Android, tvOS, macOS, and Linux automation workflows.52GoodAuth: no auth required

Verdict: choose Mobilerun for os automation work as a local process; choose Agent Device for os automation. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Mobilerun logoChoose Mobilerun when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
Explore Mobilerun

Agent Device logoChoose Agent Device when

  • You need dedicated capabilities in the OS Automation domain.
  • Its auth model fits you: No auth required.
Explore Agent Device

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMobilerun logoMobilerunAgent Device logoAgent Device
CategoryOS AutomationOS Automation
Quality signal48/100 · Fair52/100 · Good
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars9,7095,078
Directory activity 2 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Mobilerun tools

No tool names declared yet. Check the project README from the listing page.

Agent Device 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.

Mobilerun

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mobilerun": {
      "command": "uvx",
      "args": [
        "mobilerun"
      ]
    }
  }
}

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.

Frequently asked questions

Mobilerun is categorized under OS Automation and uses a local stdio subprocess. Agent Device belongs to OS Automation and uses an install path we have not confirmed yet. Pick Mobilerun for os automation work and Agent Device 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.

Mobilerun has no declared pricing — check the project's own site. Agent Device is listed as free. Auth: no auth required. 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 mobilerun and callstackincubator-agent-device as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Mobilerun has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 9,709 GitHub stars. Agent Device has 52/100 (Good) with 3 views, 0 installs and 5,078 GitHub stars.