Relay Remotify MCP server
io.github.onlsol/relay-remotify-mcp·v0.6.2·3 starsRun shell commands on remote computers with optional per-command approval, using only curl and bash.
3 stars1.4k downloads/wk
Reviews
Write oneNobody has reviewed Relay Remotify yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Relay Remotify tools (2)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
remote_session_infoReturn the current relay session: key, URLs, and the exact one-liners to paste on the remote machine to start the listener (remote_quickstart = supervised, y/N per command; remote_quickstart_auto = unattended). When you show them to the user, show BOTH verbatim in a fenced code block and make them the final message of your turn.
remote_session_resetRecover a wedged remotify session. Default (no arguments): clear stuck relay state in place - drops any queued command/result and the in-flight marker; the session key and a connected listener keep working.
Public scan report
scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 6 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Relay Remotify compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- Tools
- 2
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 3
- more than 80% of 28,688 servers
- Downloads a week
- 1,374
- more than 95% of 12,191 servers with a package
What its tools let an agent do: 2 read
Install Relay Remotify in Claude Code, Cursor or VS Code
Runs npx -y remotify-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add relay-remotify-mcp -- npx -y remotify-mcp
What the publisher says
From the Relay Remotify repository's README, as published. We do not edit it. Read it on GitHub
HTTP command relay
Ephemeral HTTP command relay. Push a shell command from any HTTP client; have it run on a remote machine that has nothing installed but curl and bash.
Useful whenever you need to bounce a command to a shell without opening an SSH port, installing an agent, or deploying anything:
- LLM coding sessions driving an arbitrary remote host - any tool, self-hosted or cloud (MCP hosts, curl-literate chat models, local runners, etc.)
- CI runners poking at post-deploy state
- Admin shells behind NAT / firewalls
- Headless devices reachable only outbound
Data on the relay is minimised, not absent: each session gets a small directory holding the pending command/result and a timestamped push history, purged as soon as the idle TTL lapses (default 3h) or on explicit delete. Session keys are 128-bit random.
Architecture
CLIENT RELAY REMOTE SHELL
(LLM / CI / terminal) (single vhost) (curl + bash)
| | |
|-- POST /api/session -------->| |
|<-- key + URLs ---------------| |
| | |
| (user pastes the remote-quickstart on the remote) |
| | |
| |<-- curl /r/KEY?mode=... -----|
| | runner script starts |
| | |
|-- POST /cmd-KEY ------------>| queued on disk |
|<-- 201 ----------------------| |
| (client may disconnect) | |
| |<-- GET /cmd-KEY (poll) ------|
| |-- 200 + command body ------->|
| | >>> prints cmd|
| | Stack
No database. No worker. The only persistent state is a flat-file queue under data/sessions// (bind-mounted from the host into the container at /var/data/sessions//), data-minimised and purged on idle TTL or explicit delete.
Quick start
cp .env.example .env
docker compose up -dThe shipped .env.example defaults to a self-consistent local HTTP setup - no editing required for a first run. After the command above, the API and the one-liners it hands out are both reachable at http://localhost:49180.
For a public deployment, edit .env first: set DOMAIN to your real hostname, SCHEME=https, NGINXMODE=tls, HTTPPORT=80 (required so Let's Encrypt's HTTP-01 challenge is reachable) and HTTPS_PORT=443, then:
docker compose --profile tls up -d # HTTP + HTTPS with automatic TLSThat's the whole install. Everything else runs in containers.
Environment
All knobs live in .env; nothing is hardcoded.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Relay Remotify: common questions
- Is Relay Remotify MCP server safe?
- Mostly: it is graded B (83/100). Read the Relay Remotify safety report
- How do I install Relay Remotify?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Relay Remotify need an API key?
- Yes. The registry entry asks for
REMOTIFY_KEY. - Is Relay Remotify maintained?
- The last commit was 27 days ago (2026-10-08). The latest release is v0.6.2.
- What can I use instead of Relay Remotify?
- Servers from other publishers that do the same job: Computer MCP server and SSH Manager MCP server.
- How does Relay Remotify compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Relay Remotify
Same job from other publishers: the closest match first, then the best rated.
- ComputerA private persistent computer: files that survive between runs, a bash shell and JavaScript.not reviewedEstablishedA
- SSH ManagerSSH for AI agents: commands, files, backups and health, with approval, a vault and an audit trailnot reviewedEstablishedA
