Linux MCP Server vs Remote Pc MCP
A side-by-side look at the Linux MCP Server 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.
Verdict: choose Linux MCP Server for os automation work as a local process; choose Remote Pc 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?
Choose 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.
Choose Remote Pc MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- 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 | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 64/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 316 | 6 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 23 | 15 |
| Full listing | View Linux MCP Server | View Remote Pc MCP |
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 processesget_process_infoGet information about a specific process.list_servicesList all systemd services.- +11 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.
Linux MCP Server
{
"mcpServers": {
"linux-mcp-server-2": {
"command": "uvx",
"args": [
"linux-mcp-server"
]
}
}
}
Remote Pc MCP
{
"mcpServers": {
"remote-pc-mcp": {
"command": "uvx",
"args": [
"remote-pc-mcp"
],
"env": {
"REMOTE_PC_MCP_TOKEN": "YOUR_REMOTE_PC_MCP_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Linux MCP Server is categorized under OS Automation and uses a local stdio subprocess. Remote Pc MCP belongs to OS Automation and uses a local stdio subprocess. Pick Linux MCP Server 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.
Linux MCP Server 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 linux-mcp-server-2 and remote-pc-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 2 views, 0 installs and 316 GitHub stars. Remote Pc MCP has 55/100 (Good) with 1 views, 0 installs and 6 GitHub stars.
