/ Annuaire / Playground / mcp-ssh-manager
● Communauté bvisible ⚡ Instantané

mcp-ssh-manager

par bvisible · bvisible/mcp-ssh-manager

37 SSH tools for managing fleets of Linux servers via Claude — execute, upload, download, backup, monitor health — with SSH-key + agent auth.

mcp-ssh-manager is a Node SSH wrapper exposing 37 tools for DevOps-style ops across multiple remote servers. Beyond raw exec/upload/download, it adds opinionated backup, health-monitoring, and DB-operation helpers. Configure via .env or TOML for named hosts.

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

ssh-manager.replay ▶ prêt
0/0

Installer

Choisissez votre 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
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "ssh-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "ssh-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "ssh-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "ssh-manager",
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json
{
  "context_servers": {
    "ssh-manager": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-ssh-manager"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : mcp-ssh-manager

Triage a fleet of VPS servers from chat

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

Quand l'utiliser : You manage 5-20 VPS boxes and need to eyeball them all quickly.

Prérequis
  • SSH key in agentssh-add ~/.ssh/id_ed25519
  • Named host list — TOML config with name → host/user/key path
Déroulement
  1. Run health checks in parallel
    For each server in my fleet, run: uptime, df -h, free -h, last error in journalctl. Summarize anything concerning.✓ Copié
    → Per-host summary + flagged issues
  2. Drill into problems
    On server X where disk is 95% full, find the top 10 largest directories under /var.✓ Copié
    → du output
  3. Fix or escalate
    Is it safe to delete /var/log/old-*.gz? Confirm with me before running.✓ Copié
    → Plan + waits for confirm

Résultat : Fleet-wide triage in 5 minutes.

Pièges
  • 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

Quand l'utiliser : You realize your important VPS has no backup and need one now, manually.

Déroulement
  1. Identify backup targets
    On server 'homelab', list directories under /home and /var that I should back up. Exclude logs and caches.✓ Copié
    → Target list
  2. Create and download archive
    Tar+gzip those into /tmp/backup-$(date +%F).tgz, then download to my local ~/Backups/.✓ Copié
    → Archive landed locally

Résultat : Ad-hoc backup in one conversation.

Pièges
  • Large backups blow remote /tmp — Stream directly: ssh host 'tar cz ...' > local.tgz (arrange via exec + download)
Combiner avec : filesystem

Deploy a small app to a VPS without leaving chat

👤 Solo devs shipping side projects ⏱ ~10 min intermediate

Quand l'utiliser : No Coolify, no Dokku — just a bare VPS and your code.

Déroulement
  1. Upload code
    Upload my ./dist/ directory to server 'myvps' at /opt/myapp/, preserving perms.✓ Copié
    → Upload complete
  2. Restart service
    On myvps, sudo systemctl restart myapp and then check status. Send me the status output.✓ Copié
    → active (running) or error

Résultat : Deploy done in 2 minutes.

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

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
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

Coût et limites

Coût d'exécution

Quota d'API
None
Tokens par appel
Exec output can be huge — | tail -50 is your friend
Monétaire
Free, MIT
Astuce
Cap long output: cmd | head -100, never cat whole log files.

Sécurité

Permissions, secrets, portée

Portées minimales : SSH key with only the needed remote permissions
Stockage des identifiants : Private keys in ~/.ssh; use SSH agent for passphrases
Sortie de données : Traffic to the hosts you configure
Ne jamais accorder : Root-equivalent keys to an agent that can also reach the internet

Dépannage

Erreurs courantes et correctifs

Permission denied (publickey)

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

Vérifier : 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').

Vérifier : ssh in and `ps aux`
rsync needs sshpass

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

Alternatives

mcp-ssh-manager vs autres

AlternativeQuand l'utiliserCompromis
Raw ssh via terminalYou're not using an LLM for opsManual, but well-understood
AnsibleYou manage 50+ hosts with reproducible playbooksHeavier; chat-driven ad-hoc not its strength

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills