/ Directory / Playground / mcp-ssh-manager
● Community bvisible ⚡ Instant

mcp-ssh-manager

by 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.

Why use it

Key features

Live Demo

What it looks like in practice

ssh-manager.replay ▶ ready
0/0

Install

Pick your 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
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

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

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

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

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

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

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

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

Continue uses an array of server objects rather than a map.

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

Add to context_servers. Zed hot-reloads on save.

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

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use mcp-ssh-manager

Triage a fleet of VPS servers from chat

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

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

Prerequisites
  • SSH key in agentssh-add ~/.ssh/id_ed25519
  • Named host list — TOML config with name → host/user/key path
Flow
  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.✓ Copied
    → 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.✓ Copied
    → du output
  3. Fix or escalate
    Is it safe to delete /var/log/old-*.gz? Confirm with me before running.✓ Copied
    → Plan + waits for confirm

Outcome: Fleet-wide triage in 5 minutes.

Pitfalls
  • 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

When to use: You realize your important VPS has no backup and need one now, manually.

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

Outcome: Ad-hoc backup in one conversation.

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

Deploy a small app to a VPS without leaving chat

👤 Solo devs shipping side projects ⏱ ~10 min intermediate

When to use: No Coolify, no Dokku — just a bare VPS and your code.

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

Outcome: Deploy done in 2 minutes.

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

Combinations

Pair with other MCPs for X10 leverage

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.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
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

Cost & Limits

What this costs to run

API quota
None
Tokens per call
Exec output can be huge — | tail -50 is your friend
Monetary
Free, MIT
Tip
Cap long output: cmd | head -100, never cat whole log files.

Security

Permissions, secrets, blast radius

Minimum scopes: SSH key with only the needed remote permissions
Credential storage: Private keys in ~/.ssh; use SSH agent for passphrases
Data egress: Traffic to the hosts you configure
Never grant: Root-equivalent keys to an agent that can also reach the internet

Troubleshooting

Common errors and fixes

Permission denied (publickey)

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

Verify: 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').

Verify: 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 others

AlternativeWhen to use it insteadTradeoff
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

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills