Mobile Device MCP vs Remote Pc MCP
A side-by-side look at the Mobile Device MCP and Remote Pc MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
Remote Pc MCPOS AutomationDrive a PC over MCP: shell, files, processes, system stats, screenshots, mouse and keyboard.49FairAuth: api key requiredVerdict: choose Mobile Device MCP for os automation work as a local process; choose Remote Pc MCP for os automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 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.
RChoose Remote Pc MCP when
- You need dedicated capabilities in the OS Automation domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
REMOTE_PC_MCP_TOKEN. - You want tools like
shell_exec, read_file, write_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R Remote Pc MCP | |
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 55/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | REMOTE_PC_MCP_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 48 | 6 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 14 | 15 |
| Full listing | View Mobile Device MCP | View Remote Pc MCP |
Tools & capabilities
Mobile Device MCP tools 14
list_devicesList available iOS and Android devicesscreenshotCapture 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: truetapTap at screen coordinatesdouble_tapDouble-tap at screen coordinateslong_pressLong-press at screen coordinates (configurable duration)scrollSwipe from start to end coordinatestype_textType text into the focused elementpress_buttonPress a hardware/navigation button (home, back, enter, volumeUp/Down, dpadUp/Down/Left/Right/Center)launch_appLaunch an app by bundle ID / package nameterminate_appForce-stop an applist_appsList installed apps- +2 more on the listing page
Remote Pc MCP tools 15
shell_execRun any shell command — returns stdout, stderr, exit coderead_fileRead a file as text or base64 (binary fallback)write_fileWrite text or binary content to a filelist_directoryList files and directories, optionally recursivesystem_infoOS, CPU, RAM, and GPU stats (NVIDIA GPUs via `nvidia-smi`; absent on non-GPU hosts)start_processStart a long-running command in the background — returns a PIDget_process_outputPoll stdout/stderr of a background process by PIDkill_processTerminate a process by PIDdownload_fileDownload a URL directly to this machinetake_screenshotCapture the primary display — returns base64-encoded PNGclickClick at screen coordinates `(x, y)` — left / right / middle, single or multi-clickmove_mouseMove cursor to `(x, y)`, optionally animated- +3 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.
Mobile Device MCP
{
"mcpServers": {
"mobile-device-mcp": {
"command": "npx",
"args": [
"-y",
"@srmorete/mobile-device-mcp@latest"
]
}
}
}
Remote Pc MCP
No confirmed install command for Remote Pc MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Mobile Device MCP is categorized under OS Automation and uses a local stdio subprocess. Remote Pc MCP belongs to OS Automation and uses an install path we have not confirmed yet. Pick Mobile Device MCP for os automation work and Remote Pc 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. Remote Pc MCP has no confirmed install command yet — follow its own setup instructions.
Mobile Device MCP has no declared pricing — check the project's own site. Remote Pc MCP is listed as free. Auth: api key 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 remote-pc-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 55/100 (Good) with 2 views, 0 installs and 48 GitHub stars. Remote Pc MCP has 49/100 (Fair) with 0 views, 0 installs and 6 GitHub stars.