Mobile Device MCP vs Windows MCP

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

Mobile Device MCP logoMobile Device MCPOS Automation · Local subprocess (stdio)Control iOS and Android devices with multi-device and seamless Native/WebView support.59GoodAuth: not declaredWindows MCP logoWindows MCPOS Automation · Local subprocess (stdio)An MCP Server for computer-use in Windows OS48FairAuth: no auth required

Verdict: choose Mobile Device MCP for os automation work as a local process; choose Windows 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?

Mobile Device MCP logoChoose 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.
Explore Mobile Device MCP

Windows MCP logoChoose Windows MCP when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Windows MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMobile Device MCP logoMobile Device MCPWindows MCP logoWindows MCP
CategoryOS AutomationOS Automation
Quality signal59/100 · Good48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars5210,147
Directory activity 4 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools14Not listed

Tools & capabilities

Mobile Device MCP tools 14

  • list_devicesList available iOS and Android devices
  • screenshotCapture 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: true
  • tapTap at screen coordinates
  • double_tapDouble-tap at screen coordinates
  • long_pressLong-press at screen coordinates (configurable duration)
  • scrollSwipe from start to end coordinates
  • type_textType text into the focused element
  • press_buttonPress a hardware/navigation button (home, back, enter, volumeUp/Down, dpadUp/Down/Left/Right/Center)
  • launch_appLaunch an app by bundle ID / package name
  • terminate_appForce-stop an app
  • list_appsList installed apps
  • +2 more on the listing page

Windows MCP 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.

Mobile Device MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mobile-device-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@srmorete/mobile-device-mcp@latest"
      ]
    }
  }
}

Windows MCP

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

Frequently asked questions

Mobile Device MCP is categorized under OS Automation and uses a local stdio subprocess. Windows MCP belongs to OS Automation and uses a local stdio subprocess. Pick Mobile Device MCP for os automation work and Windows 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.

Mobile Device MCP has no declared pricing — check the project's own site. Windows MCP 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 mobile-device-mcp and windows-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Mobile Device MCP has a quality signal of 59/100 (Good) with 4 views, 0 installs and 52 GitHub stars. Windows MCP has 48/100 (Fair) with 6 views, 0 installs and 10,147 GitHub stars.