Agent Device vs Mobilerun

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

Agent Device logoAgent DeviceOS AutomationMCP server for mobile app automation: verify, control, and debug iOS, Android, TV, and desktop apps44FairAuth: no auth requiredMobilerun logoMobilerunOS Automation · Local subprocess (stdio)Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.49FairAuth: not declared

Verdict: choose Agent Device 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?

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

Mobilerun logoChoose Mobilerun when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgent Device logoAgent DeviceMobilerun logoMobilerun
CategoryOS AutomationOS Automation
Quality signal44/100 · Fair49/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars5,1239,745
Directory activity 3 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

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

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.

Mobilerun

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

Frequently asked questions

Agent Device 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 Agent Device 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. Agent Device has no confirmed install command yet — follow its own setup instructions.

Agent Device 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 agent-device and mobilerun 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 44/100 (Fair) with 3 views, 0 installs and 5,123 GitHub stars. Mobilerun has 49/100 (Fair) with 4 views, 0 installs and 9,745 GitHub stars.