Ext Ops Panel
Open dashboard
Comparison

Remote Terminal MCP vs io.github.onlsol/relay-remotify-mcp

Remote Terminal MCP is an MCP server published by TiM00R. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.onlsol/relay-remotify-mcp is an MCP server published by onlsol. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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

Where each is published
MarketplaceRemote Terminal MCPio.github.onlsol/relay-remotify-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 (npm): 4 536
Downloads/week (npm): 718
Forks (GitHub): 0
Stars (GitHub): 3
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

Remote Terminal MCP vs io.github.onlsol/relay-remotify-mcp
FactRemote Terminal MCPio.github.onlsol/relay-remotify-mcp
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub3
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (remote-terminal-mcp)On your machine (remotify-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 02, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/onlsol/relay.remotify.run
Changes in the last 7 days00
First seen2026-10-112026-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

In its own words, on Official MCP Registry:

Complete SSH terminal for Linux with AI/user control and dual-stream visibility

io.github.onlsol/relay-remotify-mcp

In its own words, on Official MCP Registry:

Run shell commands on remote computers with optional per-command approval, using only curl and bash.

How to run each

Remote Terminal MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "REMOTE_TERMINAL_ROOT=<YOUR_REMOTE_TERMINAL_ROOT>" --transport stdio remote-terminal -- uvx remote-terminal-mcp

Requires: REMOTE_TERMINAL_ROOT

io.github.onlsol/relay-remotify-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "REMOTIFY_KEY=<YOUR_REMOTIFY_KEY>" --transport stdio relay-remotify-mcp -- npx -y remotify-mcp

Requires: REMOTIFY_KEY (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.onlsol/relay-remotify-mcp asks for

  • REMOTIFY_KEY (secret)
  • REMOTIFY_URL

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.onlsol/relay-remotify-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built