Remote Terminal MCP vs io.github.raghibrm/remote-pc-mcp
Remote Terminal MCP is an MCP server published by TiM00R. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.raghibrm/remote-pc-mcp is an MCP server published by raghibrm. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.raghibrm/remote-pc-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.3.3 Downloads/month (PyPI): 130 Downloads/week (PyPI): 32 Not marked · First seen |
Listed Version: 0.6.2 Downloads/month (PyPI): 0 Downloads/week (PyPI): 400 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.6.2 Downloads/month (PyPI): 0 Downloads/week (PyPI): 400 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Remote Terminal MCP | io.github.raghibrm/remote-pc-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 6 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | On your machine (remote-terminal-mcp) | On your machine (remote-pc-mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 3, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/raghibrm/remote-pc-mcp |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Remote Terminal MCP
Complete SSH terminal for Linux with AI/user control and dual-stream visibility
io.github.raghibrm/remote-pc-mcp
Drive a PC over MCP: shell, files, processes, system stats, screenshots, mouse and keyboard.
How to run each
Remote Terminal MCP As a local MCP server: PyPI package
claude mcp add --env "REMOTE_TERMINAL_ROOT=<YOUR_REMOTE_TERMINAL_ROOT>" --transport stdio remote-terminal -- uvx remote-terminal-mcpRequires: REMOTE_TERMINAL_ROOT
io.github.raghibrm/remote-pc-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: REMOTE_PC_MCP_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Remote Terminal MCP asks for
REMOTE_TERMINAL_ROOT
Only io.github.raghibrm/remote-pc-mcp asks for
REMOTE_PC_MCP_HOSTREMOTE_PC_MCP_PORTREMOTE_PC_MCP_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Remote Terminal MCP · What it can do: io.github.raghibrm/remote-pc-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.