mcp-ssh-manager MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

37 tools spanning core SSH ops + DevOps helpers
Multi-host named configs via .env or TOML
Auth: SSH keys (preferred), SSH agent (for passphrase keys), passwords
Backup + health-monitor tools built in
rsync file sync (requires sshpass for password auth)

Live-Demo

In der Praxis

ssh-manager.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "ssh-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "ssh-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "ssh-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "ssh-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "ssh-manager",
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "ssh-manager": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-ssh-manager"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add ssh-manager -- npx -y mcp-ssh-manager

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: mcp-ssh-manager

Triage a fleet of VPS servers from chat

👤 Solo ops, small team SREs ⏱ ~15 min intermediate

Wann einsetzen: You manage 5-20 VPS boxes and need to eyeball them all quickly.

Voraussetzungen

SSH key in agent — ssh-add ~/.ssh/id_ed25519
Named host list — TOML config with name → host/user/key path

Ablauf

Run health checks in parallel

For each server in my fleet, run: uptime, df -h, free -h, last error in journalctl. Summarize anything concerning.✓ Kopiert

→ Per-host summary + flagged issues
Drill into problems

On server X where disk is 95% full, find the top 10 largest directories under /var.✓ Kopiert

→ du output
Fix or escalate

Is it safe to delete /var/log/old-*.gz? Confirm with me before running.✓ Kopiert

→ Plan + waits for confirm

Ergebnis: Fleet-wide triage in 5 minutes.

Fallstricke

Command timeouts are advisory — a hung command can leave processes running — Use timeout 30 <cmd> explicitly for anything that could hang

Take a one-shot backup from a remote server

👤 Home-lab admins, solo devs ⏱ ~15 min intermediate

Wann einsetzen: You realize your important VPS has no backup and need one now, manually.

Ablauf

Identify backup targets

On server 'homelab', list directories under /home and /var that I should back up. Exclude logs and caches.✓ Kopiert

→ Target list
Create and download archive

Tar+gzip those into /tmp/backup-$(date +%F).tgz, then download to my local ~/Backups/.✓ Kopiert

→ Archive landed locally

Ergebnis: Ad-hoc backup in one conversation.

Fallstricke

Large backups blow remote /tmp — Stream directly: ssh host 'tar cz ...' > local.tgz (arrange via exec + download)

Kombinieren mit: filesystem

Deploy a small app to a VPS without leaving chat

👤 Solo devs shipping side projects ⏱ ~10 min intermediate

Wann einsetzen: No Coolify, no Dokku — just a bare VPS and your code.

Ablauf

Upload code

Upload my ./dist/ directory to server 'myvps' at /opt/myapp/, preserving perms.✓ Kopiert

→ Upload complete
Restart service

On myvps, sudo systemctl restart myapp and then check status. Send me the status output.✓ Kopiert

→ active (running) or error

Ergebnis: Deploy done in 2 minutes.

Fallstricke

sudo password required — Configure NOPASSWD for the specific service in /etc/sudoers.d/

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

ssh-manager + filesystem

Download a remote file + edit locally + upload back

Download /etc/nginx/sites-enabled/example.conf, edit to add gzip_comp_level 6, upload and restart nginx.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
execute	host, command, timeout?: int	Any remote shell command	free
upload	host, local_path, remote_path	Send a file or directory	free
download	host, remote_path, local_path	Pull a file from a server	free
sync	host, local, remote, delete?: bool	Bulk dir sync via rsync	free
health_check	host	Quick pulse	free

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None
Tokens pro Aufruf: Exec output can be huge — | tail -50 is your friend
Kosten in €: Free, MIT
Tipp: Cap long output: cmd | head -100, never cat whole log files.

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: SSH key with only the needed remote permissions

Credential-Speicherung: Private keys in ~/.ssh; use SSH agent for passphrases

Datenabfluss: Traffic to the hosts you configure

Niemals gewähren: Root-equivalent keys to an agent that can also reach the internet

Never commit .env or TOML with private keys to a repo.
Windows remote hosts need PLATFORM=windows to skip Linux-specific wrappers.
Timeouts are advisory — use explicit timeout N inside the command for hard limits.

Fehlerbehebung

Häufige Fehler und Lösungen

Permission denied (publickey)

Key not in agent, or remote ~/.ssh/authorized_keys wrong. ssh-add -l to verify.

Prüfen: ssh -i key host 'echo ok' directly first

Command timeout but process still running remotely

Wrap command with timeout: execute('host', 'timeout 30 long-command').

Prüfen: ssh in and `ps aux`

rsync needs sshpass

Either install sshpass on local or switch to SSH key auth for that host.

Alternativen

mcp-ssh-manager vs. andere

Alternative	Wann stattdessen	Kompromiss
Raw ssh via terminal	You're not using an LLM for ops	Manual, but well-understood
Ansible	You manage 50+ hosts with reproducible playbooks	Heavier; chat-driven ad-hoc not its strength

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen