Computer Use vs Mobilerun

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

Computer Use logoComputer UseOS Automation · Local subprocess (stdio)Control your computer with screenshots, mouse, and keyboard automation.49FairAuth: not declaredMobilerun logoMobilerunOS Automation · Local subprocess (stdio)Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.49FairAuth: not declared

Verdict: choose Computer Use 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?

Computer Use logoChoose Computer Use when

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

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.

SpecComputer Use logoComputer UseMobilerun logoMobilerun
CategoryOS AutomationOS Automation
Quality signal49/100 · Fair49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3879,746
Directory activity 2 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Computer Use 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.

Computer Use

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "computer-use": {
      "command": "npx",
      "args": [
        "-y",
        "computer-use-mcp"
      ]
    }
  }
}

Mobilerun

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

Frequently asked questions

Computer Use is categorized under OS Automation and uses a local stdio subprocess. Mobilerun belongs to OS Automation and uses a local stdio subprocess. Pick Computer Use 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.

Computer Use has no declared pricing — check the project's own site. 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 computer-use and mobilerun as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Computer Use has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 387 GitHub stars. Mobilerun has 49/100 (Fair) with 7 views, 0 installs and 9,746 GitHub stars.