Ermöglicht es AI Agents, Befehle auszuführen, Dateien zu verschieben und Remote-Maschinen via SSH mithilfe strukturierter Tools und bestehender OpenSSH-Konfigurationen zu auditieren.
Auch bekannt als hypnosis/ssh-mcp-server, ssh-mcp-server, @hypnosis/ssh-mcp-server
- Stars
- 11
- Tools
- 18
- Downloads, 30 Tage
- 944
- Neueste Version
- 2.3.3
- Letzter Commit
- 13. Nov. 2026
- Lizenz
- MIT
Was ist SSH MCP?
Ermöglicht es AI Agents, Befehle auszuführen, Dateien zu verschieben und Remote-Maschinen via SSH mithilfe strukturierter Tools und bestehender OpenSSH-Konfigurationen zu auditieren. Er stellt 18 Tools bereit, etwa ssh_exec, ssh_file_read, ssh_file_write.
Zusammenfassung generiert aus dem README des Projekts
Über SSH MCP server
Das Management von Remote-Infrastruktur durch AI Agents wird mit diesem Tool effizienter, da es das Ausführen von Befehlen, das Verschieben von Dateien und das Auditieren von Maschinen via SSH ermöglicht. Es wurde für DevOps Engineers, Sysadmins und Developer entwickelt, die Cloud-VPS-Instanzen, Bare-Metal-Server oder sogar Legacy-Hardware wie Router und NAS-Geräte warten müssen. Anstatt eine rohe Shell bereitzustellen, die durch ASCII-Tabellen und Log-Dumps massiv Tokens verbraucht, liefert es strukturierte Daten über spezifische Tools wie ssh_snapshot und ssh_audit_baseline.
Der Server läuft lokal und nutzt den vorhandenen OpenSSH-Client auf deinem Rechner, was bedeutet, dass deine aktuellen Keys, die ~/.ssh/config, Jump Hosts und das Agent Forwarding respektiert werden. Er erfordert Node.js 18+ und einen systemeigenen ssh-Client in deinem PATH. Nutzer können Verbindungen über eine JSON-Profil-Datei konfigurieren, um Hosts, Usernamen und Pfade zu privaten Keys zu definieren. Er lässt sich in verschiedene MCP-Clients integrieren, darunter Claude Code, Codex CLI, Cline und Gemini CLI.
Was du damit machen kannst
- 1Remote-System-Audits durchführenEin AI Agent kann ein umfassendes Baseline-Audit durchführen, um Festplatte, Arbeitsspeicher und den Status von Services in einem Durchgang zu prüfen.
- 2Server-Performance troubleshootenDu kannst eine KI fragen, ob eine bestimmte Maschine gesund ist, indem du einen strukturierten Snapshot ihres aktuellen Zustands abrufst.
- 3Dateien auf Legacy-Hardware verwaltenDer Server kann automatisch ältere Protokolle nutzen, um Dateien auf ältere Router oder NAS-Geräte zu übertragen, die modernes scp nicht unterstützen.
- 4AI-Token-Verbrauch reduzierenDeveloper können Geld und Platz im Context Window sparen, indem sie strukturierte Tools anstelle von rohem Terminal-Output verwenden.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du SSH MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenSSH MCP in Claude Code installieren
$ claude mcp add --env 'SSH_PROFILES_FILE=<SSH_PROFILES_FILE>' ssh-mcp-server -- npx -y @hypnosis/ssh-mcp-serverSSH MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"ssh-mcp-server": {
"command": "npx",
"args": [
"-y",
"@hypnosis/ssh-mcp-server"
],
"env": {
"SSH_PROFILES_FILE": "<SSH_PROFILES_FILE>"
}
}
}
}SSH MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"ssh-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hypnosis/ssh-mcp-server"
],
"env": {
"SSH_PROFILES_FILE": "<SSH_PROFILES_FILE>"
}
}
}
}SSH MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"ssh-mcp-server","type":"stdio","command":"npx","args":["-y","@hypnosis/ssh-mcp-server"],"env":{"SSH_PROFILES_FILE":"<SSH_PROFILES_FILE>"}}'SSH MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"ssh-mcp-server": {
"command": "npx",
"args": [
"-y",
"@hypnosis/ssh-mcp-server"
],
"env": {
"SSH_PROFILES_FILE": "<SSH_PROFILES_FILE>"
}
}
}
}SSH MCP in Codex installieren
$ codex mcp add ssh-mcp-server --env 'SSH_PROFILES_FILE=<SSH_PROFILES_FILE>' -- npx -y @hypnosis/ssh-mcp-serverSSH MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.ssh-mcp-server] command = "npx" args = ["-y", "@hypnosis/ssh-mcp-server"] [mcp_servers.ssh-mcp-server.env] SSH_PROFILES_FILE = "<SSH_PROFILES_FILE>"
SSH MCP in Gemini CLI installieren
$ gemini mcp add -s user -e 'SSH_PROFILES_FILE=<SSH_PROFILES_FILE>' ssh-mcp-server npx -- -y @hypnosis/ssh-mcp-serverSSH MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"ssh-mcp-server": {
"command": "npx",
"args": [
"-y",
"@hypnosis/ssh-mcp-server"
],
"env": {
"SSH_PROFILES_FILE": "<SSH_PROFILES_FILE>"
}
}
}
}SSH MCP tools 18
Erkannt aus dem READMEssh_execssh_file_readssh_file_writessh_file_listssh_uploadssh_downloadssh_job_statusssh_job_outputssh_job_listssh_job_killssh_log_tailssh_log_search
| ssh_exec | — | |
| ssh_file_read | — | |
| ssh_file_write | — | |
| ssh_file_list | — | |
| ssh_upload | — | |
| ssh_download | — | |
| ssh_job_status | — | |
| ssh_job_output | — | |
| ssh_job_list | — | |
| ssh_job_kill | — | |
| ssh_log_tail | — | |
| ssh_log_search | — |
Alle 18 Tools anzeigenWeniger Tools anzeigen
ssh_snapshotssh_monitorssh_audit_baselinessh_tls_checkssh_disk_breakdownssh_service_status
| ssh_snapshot | — | |
| ssh_monitor | — | |
| ssh_audit_baseline | — | |
| ssh_tls_check | — | |
| ssh_disk_breakdown | — | |
| ssh_service_status | — |
Konfiguration
SSH_PROFILES_FILEErforderlichAbsolute path to the JSON file describing the servers this agent may reach.
SSH_MCP_LOG_LEVELLog verbosity: error, warn, info or debug. Defaults to info.
| Name | Beschreibung | Typ |
|---|---|---|
| SSH_PROFILES_FILE | Absolute path to the JSON file describing the servers this agent may reach. | Erforderlich |
| SSH_MCP_LOG_LEVEL | Log verbosity: error, warn, info or debug. Defaults to info. |
Automatisierte Checks
Geluften am 12. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageBestanden
- Remote Endpoint nutzt HTTPSNicht geprüft
- Destruktive Tools sind markiertBestanden
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenBestanden
README
Auf GitHub ansehenSSH MCP Server — Remote server tools for AI agents
It uses the OpenSSH client already on your machine: your keys, your ~/.ssh/config, your jump hosts, your agent forwarding. Nothing bundled, nothing to compile, no native bindings.
Works with Claude Code, Codex CLI, Cline, opencode, Gemini CLI, Qwen Code, Hermes and other MCP clients.
Install · Tools · Setup · Security · Roadmap · Docs · Changelog
Install in 30 seconds
No global installation required. npx downloads the package on first use:
npx -y @hypnosis/ssh-mcp-server
Add it to your MCP client — Claude Code, for example — for every project:
claude mcp add ssh -s user \
-e SSH_PROFILES_FILE="$HOME/.claude/ssh-profiles.json" \
-- npx -y @hypnosis/ssh-mcp-server
Or write it by hand — the same server in the config shape most clients share:
{
"mcpServers": {
"ssh": {
"command": "npx",
"args": ["-y", "@hypnosis/ssh-mcp-server"],
"env": {
"SSH_PROFILES_FILE": "~/.claude/ssh-profiles.json"
}
}
}
}
Then create ~/.claude/ssh-profiles.json with at least one machine:
{
"profiles": {
"production": {
"host": "server.example.com",
"username": "admin",
"privateKeyPath": "~/.ssh/your_private_key"
}
}
}
That is enough to connect.
Codex, opencode, Qwen Code and other clients are covered in Set up the SSH MCP server.
Install as a plugin
Some clients — Claude Code, for example — can take the whole thing as a plugin instead:
/plugin marketplace add hypnosis/ssh-mcp-server
/plugin install ssh-mcp-server@ssh-mcp-server
The plugin reads ~/.claude/ssh-profiles.json unless SSH_PROFILES_FILE says otherwise, so
create that file first and the server comes up with your machines already loaded.
Requirements
Node.js 18+ and a system ssh client on PATH. On Windows, use a key-based profile;
password and passphrase profiles are not currently available.
Prefer a pinned version, offline work, or one less registry check per launch:
npm install -g @hypnosis/ssh-mcp-server, then use ssh-mcp-server as the command instead
of npx.
Who this is for
- DevOps and SREs who want faster audits, incident checks and routine server work.
- Vibe coders and indie builders who ship with an AI assistant and run what they build on their own servers.
- Sysadmins and platform engineers who want structured tools instead of an unrestricted raw shell.
- Developers and small teams running their own VPS without a dedicated operations team.
- Homelab, NAS and router owners whose useful hardware has outlived its modern protocols.
Why an SSH MCP server instead of a raw shell
Fewer tokens, lower AI costs
A raw shell gives an AI agent a firehose: repeated commands, ASCII tables and log dumps. It burns tokens turning that noise into a picture of the server — your money.
Faster server debugging
Purpose-built tools batch routine checks, cap noisy output and return the part that matters. The agent spends less time translating terminal output and gets to the fix sooner.
Less guesswork, fewer AI mistakes
Structured answers say what was found, what could not be measured and what was truncated. That leaves the agent less room to fill gaps with a hallucination — and gives you fewer bad fixes, calmer deploys and more reliable code.
SSH compatibility: modern servers, legacy gear and Windows
Use your existing OpenSSH setup
No bundled SSH implementation, no native bindings, no rebuild per platform. Commands ride the
system ssh client, so your keys, your ~/.ssh/config, your jump hosts and your agent
forwarding all keep working exactly as they do in a terminal. When supported, one shared
multiplexed connection per destination means you authenticate once, not once per command.
SSH support for legacy servers, routers and NAS devices
Send a file to a router with a modern scp and you get this:
scp app.conf router:/etc/
# scp: subsystem request failed on channel 0
Nothing is broken — a current scp speaks the new protocol, and the router does not know it.
In a terminal you now go read a forum thread and come back with an extra flag. Here you do
nothing: the transfer is tried, the refusal is recognized, the old protocol is used instead,
and that machine is remembered so the next file goes straight there.
Fallbacks for older SSH clients and missing tools
Old gear gets a fallback, not a dead end. When a modern feature is missing, the server takes the older road where it can:
| Your machine | What you get |
|---|---|
| A router or NAS too small for modern file transfer | The file still lands — the old protocol is used automatically |
| A server from ten years ago | The workflow still works; it just opens a fresh connection per command instead of reusing one |
| A stripped-down image with no way to hash a file | The upload says "could not verify" instead of claiming a match nobody checked |
| A box where a tool simply is not installed | The answer says "not measured" — never a zero that reads as "nothing there" |
Built for the Model Context Protocol
Built on the official MCP SDK, TypeScript throughout, 2500+ unit tests plus a live suite that runs against real containers rather than mocks.
Raw SSH vs an SSH MCP server: the same job, both ways
SSH server health check
Situation: A deploy just went out. The server feels slow, and you do not know whether disk, memory, services, containers or errors are to blame.
Question: “Is this box healthy?”
Raw SSH
$ uptime
10:42:17 up 18 days, 3:21, 2 users, load average: 0.42, 0.31, 0.28
$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda1 ext4 40G 35G 5.0G 87% /
overlay overlay 40G 35G 5.0G 87% /var/lib/docker/overlay2/...
$ free -h
total used free shared buff/cache available
Mem: 7.7Gi 4.9Gi 612Mi 121Mi 2.2Gi 2.5Gi
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● api-worker.service loaded failed failed API background worker
$ docker ps -a
CONTAINER ID IMAGE STATUS PORTS
8e14d0b41c2a api:latest Up 3 minutes 0.0.0.0:8080->8080/tcp
65b894af2430 worker:latest Exited (1) 2 minutes ago
$ ss -tulpn
Netid State Local Address:Port Process
tcp LISTEN 0.0.0.0:22 users:(("sshd",pid=842,fd=3))
tcp LISTEN 0.0.0.0:8080 users:(("docker-proxy",pid=1942,fd=4))
$ journalctl -p err --since -1h | tail -50
Aug 20 10:39:14 prod api-worker[22104]: database connection timed out
Aug 20 10:39:14 prod systemd[1]: api-worker.service: Failed with result 'exit-code'.
That is still an abridged result. A complete check needs more commands for CPU, service
states, container counts and recent errors, each with its own output format. Worse, a box
without ss can look like it has zero listeners when the port check never ran.
Structured MCP result
ssh_snapshot({ "profile": "production" })
{
"disk_pct": 87,
"mem_pct": 64,
"cpu_pct": 12,
"load": "0.42 0.31 0.28",
"containers": 7,
"ports": 14,
"services_running": 3,
"recent_errors": 21,
"unavailable": []
}
What the agent gains
| Raw SSH | Structured MCP | Your gain |
|---|---|---|
| Several commands and ASCII tables | Named fields in one result | One call, named fields and fewer round trips |
| A missing tool can look like empty output | unavailable names what was not measured |
Less guessing and fewer bad fixes |
| You sort through disks, services and errors | The problem signals are already surfaced | Faster debugging |
A full ssh_audit_baseline result can be longer than a handful of raw command outputs —
about 1,077 tokens versus 765 in our lab measurement. The saving comes from the complete
workflow, not from making one response shorter.
In a real troubleshooting session, purpose-built tools reduced 49 separate command calls to 4 MCP calls. Every additional call starts another model turn with the accumulated conversation. Prompt caching can reduce the cost of repeated input, but new commands and their output still consume context. Fewer round trips mean fewer tokens across the session, less repeated analysis and a faster path to the answer.
Need the whole picture rather than the pulse? ssh_audit_baseline batches system, disk,
memory, ports, sshd, failed units, Docker, firewall and updates. Findings arrive as
CRITICAL / WARNING / OK; unmeasured sections are named instead of silently reading as zero.
Linux server log search
Situation: The API is timing out, but the same message may be in nginx, syslog, journald or an application log you cannot read with your normal user.
Question: “Where did that error come from?”
Raw SSH
$ grep -i "timeout" /var/log/nginx/error.log
2026/08/20 10:38:54 [error] upstream timed out while reading response header
$ grep -i "timeout" /var/log/syslog
Aug 20 10:39:14 prod api-worker[22104]: database connection timed out
$ grep -i "timeout" /var/log/app/*.log 2>/dev/null
$ journalctl -u api --since "1 hour ago" | grep -i timeout
Aug 20 10:39:14 prod api[22104]: database connection timed out after 30000ms
The third command looks clean, but 2>/dev/null also hid a permission error. "Nothing
matched" and "nothing was read" now look identical. A busy log can also return thousands of
lines and push the rest of the incident out of the agent's context.
Structured MCP result
ssh_log_search({ "profile": "production",
"path": ["/var/log/nginx/error.log", "/var/log/syslog", "/var/log/app/*.log"],
"query": "timeout", "context": 2, "since": "1h" })
{
"matches": 34,
"lines": [
{ "file": "/var/log/nginx/error.log", "line": 4821,
"text": "upstream timed out while reading response header", "context": false },
{ "file": "/var/log/nginx/error.log", "line": 4822,
"text": "client closed connection", "context": true }
],
"files_searched": 6,
"files_unreadable": ["/var/log/app/private"],
"files_skipped": 12,
"files_undated": [],
"limited": false,
"truncated": false
}
What the agent gains
| Raw SSH | Structured MCP | Your gain |
|---|---|---|
| Four searches and four outputs | One search across files and globs | Fewer tokens and round trips |
| Permission errors can disappear | files_unreadable names every missed path |
No false "logs are clean" conclusion |
| Output can grow without a useful ceiling | limited and truncated expose every cutoff |
Safer decisions from partial results |
since uses the server's clock, namesOnly: true returns only matching paths, and
ssh_log_tail reads the last N lines from several logs in one call.
Safe remote config edits
Situation: You need to replace an nginx config on a live server. A dropped connection, wrong mode or unchecked copy could leave the service with a broken file.
Question: “Can I replace this config without leaving a partial file?”
Raw SSH
$ sudo sh -c 'cat > /etc/nginx/conf.d/api.conf' <<'EOF'
server {
listen 80;
location / { proxy_pass http://127.0.0.1:8080; }
}
EOF
$ echo $?
0
Exit code zero says the shell finished. It does not prove which bytes landed, and >
truncated the old file before the first byte of the new one arrived. If the connection drops
mid-write, the service is left with a partial config.
Structured MCP result
ssh_file_write({ "profile": "production",
"files": [{ "path": "/etc/nginx/conf.d/api.conf",
"content": "server {\n listen 80;\n location / { proxy_pass http://127.0.0.1:8080; }\n}\n",
"mode": "644", "sudo": true, "verify": true }] })
{
"files": [{ "path": "/etc/nginx/conf.d/api.conf", "written": true,
"verified": "verified", "reason": null, "bytes": 79 }]
}
What the agent gains
| Raw SSH | Structured MCP | Your gain |
|---|---|---|
| The target is truncated before the copy completes | A complete temp file replaces it with one rename | No half-written config |
| Exit code only | Bytes and verification outcome are named | You know what actually landed |
| Permissions live inside shell text | sudo, mode and verify are per-file fields |
Predictable ownership and fewer quoting mistakes |
verified has three honest outcomes: verified, unavailable when the server has no hash
tool, and skipped when verification was not requested. For reads, ssh_file_read accepts a
list of paths; ssh_file_list handles globs, recursion, sizes and modes.
Run batch SSH commands with sudo
Situation: A deploy is ready, but nginx syntax, service state and recent errors must all be checked before traffic moves. One failed check should not disappear inside a combined dump.
Question: “Did every preflight check pass?”
Raw SSH
$ ssh admin@server.example.com 'sudo nginx -t'
nginx: configuration file /etc/nginx/nginx.conf test is successful
$ ssh admin@server.example.com 'sudo systemctl is-active nginx'
active
$ ssh admin@server.example.com 'sudo tail -5 /var/log/nginx/error.log'
2026/08/20 10:38:54 [error] upstream timed out while reading response header
Three connections return three unrelated outputs. If the commands are joined with ;, the
shell reports only the last exit code; if they are joined with &&, later checks disappear
after the first failure.
Structured MCP result
ssh_exec({ "profile": "production",
"command": ["nginx -t", "systemctl is-active nginx",
"tail -5 /var/log/nginx/error.log"],
"sudo": true })
{
"commands": [
{ "command": "nginx -t", "exit_code": 0, "truncated": false, "clipped_bytes": 0,
"stdout": "", "stderr": "nginx: configuration file /etc/nginx/nginx.conf test is successful\n" },
{ "command": "systemctl is-active nginx", "exit_code": 0, "truncated": false,
"clipped_bytes": 0, "stdout": "active\n", "stderr": "" },
{ "command": "tail -5 /var/log/nginx/error.log", "exit_code": 0, "truncated": false,
"clipped_bytes": 0, "stdout": "2026/08/21 09:14:02 [error] upstream timed out\n", "stderr": "" }
],
"job_id": null
}
What the agent gains
| Raw SSH | Structured MCP | Your gain |
|---|---|---|
| Three calls and unrelated outputs | One ordered command list | Fewer round trips |
| A combined shell can hide intermediate status | Every command keeps its own exit_code |
No missed failed check |
sudo and quoting are repeated in command text |
sudo applies to the whole batch |
Fewer quoting mistakes |
The destructive-command guard checks the complete list before the first command runs. If one entry is refused, every other entry is marked as not run and nothing is sent to the server.
Each command carries its own stdout and stderr. A command that ran and printed nothing
has an empty string; a command that never ran has no such field at all, so the two cannot be
confused. Output over 128 KB per command keeps both ends — the head for tables, the tail for
logs — with a seam in between naming the amount, and clipped_bytes says how much was cut.
Cutting happens on byte boundaries and steps back to the edge of a character, so a clipped
answer never carries a replacement mark.
sudo reaches the server without a terminal: the profile's answer is handed to sudo on
standard input. Which secret that is comes from sudoPassword when the profile names one and
from password otherwise — a profile that logs in by key has no login password at all, and
where a machine keeps the two apart the login one is the wrong answer. Where there is nothing
to answer with, the reply says so and names the ways out, instead of leaving sudo's own advice
about -S and askpass helpers. A command that reads its own standard input is never given the
password, which would otherwise end up mixed into the data.
Run long-lived SSH jobs
Situation: A backup or migration will run longer than the agent session. The connection may close, but you still need its state, output and exit code later.
Question: “Will this job survive the conversation?”
Raw SSH
$ ssh admin@server.example.com 'pg_dump app | gzip > /srv/backups/app.sql.gz'
client_loop: send disconnect: Broken pipe
The terminal is gone. You now have to reconnect, find the process, inspect the target file and guess whether the backup finished or stopped halfway.
Structured MCP result
ssh_exec({ "profile": "production",
"command": "pg_dump app | gzip > /srv/backups/app.sql.gz",
"detach": true })
{
"commands": [{
"command": "pg_dump app | gzip > /srv/backups/app.sql.gz",
"exit_code": null,
"truncated": false,
"timed_out": false,
"blocked": false,
"blocked_reason": null,
"not_run": false,
"warning": null
}],
"job_id": "mst0f2q1-9ab3c4d5"
}
What the agent gains
| Raw SSH | Structured MCP | Your gain |
|---|---|---|
| The job is tied to one SSH session | The remote job has a persistent id | Safe disconnects and restarts |
| Reconnecting means searching processes and files | Status and exit code have named states | No guessing whether it finished |
| Reading output again repeats old text | Output continues from a byte offset | Lower token use on long jobs |
Job state lives on the remote disk, not in this server's memory. ssh_job_status distinguishes
running, finished and lost; ssh_job_output continues from the last byte offset; and
ssh_job_kill signals the whole process group instead of only its shell.
Transfer files to legacy routers and NAS devices
Situation: A current OpenSSH client tries SFTP, but the router or NAS only understands the classic scp protocol. The file must still arrive intact and replace its target safely.
Question: “Can this old device still receive a verified file?”
Raw SSH
$ scp app.conf operator@router:/etc/app.conf
subsystem request failed on channel 0
scp: Connection closed
The usual next step is to remember the legacy flag, retry the copy and then run a separate hash command—if the device has a hash tool at all.
Structured MCP result
ssh_upload({ "profile": "router", "local_path": "./app.conf",
"remote_path": "/etc/app.conf", "sudo": true,
"mode": "644", "owner": "root:root", "verify": true })
{
"files": [{
"path": "/etc/app.conf",
"written": true,
"verified": "verified",
"reason": null,
"bytes": 1284
}]
}
What the agent gains
| Raw SSH | Structured MCP | Your gain |
|---|---|---|
| Modern SFTP mode stops at the first error | Classic scp fallback is automatic and remembered | Old gear still works |
| A successful copy does not prove integrity | SHA-256 verification has a named outcome | Corruption is not mistaken for success |
| Direct replacement can leave a partial target | A temp file is moved into place after transfer | The working file survives interruptions |
If the device has neither sha256sum nor openssl, the result says unavailable and names
the reason instead of reporting a false match. Whole directories use recursive: true and
verify their hashes in one batch.
Destructive command protection for AI agents
The guard runs locally, before a command reaches SSH. It separates operations that can be recovered from those that destroy the container holding the data, and it checks command order inside chains and batches.
Stop a destructive chain before it starts
A safe backup-and-replace sequence:
cp -r /srv/app /srv/app.bak && mv /srv/app /srv/app-old && rm -rf /srv/app
The same operations in the wrong order:
rm -rf /srv/app && cp -r /srv/app /srv/app.bak && mv /srv/app /srv/app-old
# REFUSED before the first command runs
The shell would delete the directory and only then discover that the backup source is gone.
The guard sees that later steps read a target already destroyed by an earlier step, so the
whole call stays on your machine. The same check catches
dropdb app && pg_dump app > backup.sql.
SSH MCP Fragen
Wie füge ich SSH MCP zu Claude Code hinzu?
Führe claude mcp add --env 'SSH_PROFILES_FILE=<SSH_PROFILES_FILE>' ssh-mcp-server -- npx -y @hypnosis/ssh-mcp-server in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich SSH MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet SSH MCP?
Er stellt 18 Tools bereit, darunter ssh_exec, ssh_file_read, ssh_file_write, ssh_file_list, ssh_upload.
Ist eine separate SSH-Installation erforderlich?
Nein, es nutzt den OpenSSH-Client, der bereits auf deinem Rechner installiert ist, inklusive deiner vorhandenen Keys, Config und Jump Hosts.
Funktioniert es auch mit älterer Hardware wie Routern oder NAS-Geräten?
Ja, der Server enthält Fallbacks für Legacy-Hardware, wie zum Beispiel die automatische Nutzung älterer Protokolle, falls moderne Features wie neue scp-Protokolle nicht unterstützt werden.
Wie geht das Tool mit fehlenden Tools auf einer Remote-Maschine um?
Anstatt eine Null zurückzugeben, die missverstanden werden könnte, gibt es explizit an, dass die Messung nicht verfügbar war.
Was sind die Systemanforderungen?
Du benötigst Node.js 18+ und einen systemeigenen ssh-Client, der in deinem PATH verfügbar ist.