Linux MCP Server vs Mobile Device MCP

A side-by-side look at the Linux MCP Server 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.

Linux MCP Server logoLinux MCP ServerOS Automation · Local subprocess (stdio)MCP server for read-only Linux system administration, diagnostics, and troubleshooting64GoodAuth: not declaredMobile Device MCP logoMobile Device MCPOS Automation · Local subprocess (stdio)Control iOS and Android devices with multi-device and seamless Native/WebView support.59GoodAuth: not declared

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

Linux MCP Server logoChoose Linux MCP Server when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_journal_logs, read_log_file, get_network_interfaces.
Explore Linux MCP Server

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecLinux MCP Server logoLinux MCP ServerMobile Device MCP logoMobile Device MCP
CategoryOS AutomationOS Automation
Quality signal64/100 · Good59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars31452
Directory activity 3 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools2314

Tools & capabilities

Linux MCP Server tools 23

  • get_journal_logsGet systemd journal logs.
  • read_log_fileRead a specific log file.
  • get_network_interfacesGet detailed information about network interfaces including address and traffic statistics.
  • get_network_connectionsGet detailed information about active network connections.
  • get_listening_portsGet details on listening port, protocols, and services.
  • pcp_guideReturns the PCP metrics guide: a catalog of the metric names recorded on a typical Linux system, and how to read the values the other PCP tools return. Read it before investigating performance with PCP, and take metric names from it rather than from memory.
  • pcp_list_metricsBrowses the PCP metric namespace. Lists the metrics under 'prefix' with their descriptions, collapsing any large sub-namespace to one line giving its name and how many metrics it holds; call again with that name as the prefix to see inside it. Only metrics this system's pmlogger records are listed, so everything listed can be passed to pcp_query_metrics. The pcp_guide tool already names the commonly needed metrics, so reach for this when you need a subsystem the guide does not cover. Use only if get_system_information() indicates PCP is available.
  • pcp_query_metricsRetrieves historical metric data from PCP archives as JSON samples. When start_time, end_time, or interval is omitted, reasonable defaults are chosen, targeting one hour or about 20 samples. Call pcp_guide first for the metric catalog and how to read the values; do not guess metric names. Use only if get_system_information() indicates PCP is available.
  • pcp_performance_summaryProduces a condensed snapshot of CPU, memory, disk, network, and process information using pcp xsos. Can summarize the live system or a particular time in the past. Use only if get_system_information() indicates PCP is available.
  • list_processesList running processes
  • get_process_infoGet information about a specific process.
  • list_servicesList all systemd services.
  • +11 more on the listing page

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

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.

Linux MCP Server

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

Mobile Device MCP

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

Frequently asked questions

Linux MCP Server is categorized under OS Automation and uses a local stdio subprocess. Mobile Device MCP belongs to OS Automation and uses a local stdio subprocess. Pick Linux MCP Server 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.

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

On AllMCPs, Linux MCP Server has a quality signal of 64/100 (Good) with 3 views, 0 installs and 314 GitHub stars. Mobile Device MCP has 59/100 (Good) with 4 views, 0 installs and 52 GitHub stars.