mcp-ssh-manager MCP — ユースケース, インストール & ライブデモ

なぜ使うのか

主な機能

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)

ライブデモ

実際の動作

ssh-manager.replay ▶ 準備完了

0/0

インストール

クライアントを選択

~/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
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

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

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

Cursor は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

VS Code → Cline → MCP Servers → Edit

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

Cline サイドバーの MCP Servers アイコンをクリックし、"Edit Configuration" を選択。

~/.codeium/windsurf/mcp_config.json

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

Claude Desktop と同じ形式。Windsurf を再起動して反映。

~/.continue/config.json

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

Continue はマップではなくサーバーオブジェクトの配列を使用。

~/.config/zed/settings.json

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

context_servers に追加。保存時に Zed がホットリロード。

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

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方： mcp-ssh-manager

Triage a fleet of VPS servers from chat

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

使うタイミング： You manage 5-20 VPS boxes and need to eyeball them all quickly.

前提条件

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

フロー

Run health checks in parallel

For each server in my fleet, run: uptime, df -h, free -h, last error in journalctl. Summarize anything concerning.✓ コピーしました

→ Per-host summary + flagged issues
Drill into problems

On server X where disk is 95% full, find the top 10 largest directories under /var.✓ コピーしました

→ du output
Fix or escalate

Is it safe to delete /var/log/old-*.gz? Confirm with me before running.✓ コピーしました

→ Plan + waits for confirm

結果： Fleet-wide triage in 5 minutes.

注意点

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

使うタイミング： You realize your important VPS has no backup and need one now, manually.

フロー

Identify backup targets

On server 'homelab', list directories under /home and /var that I should back up. Exclude logs and caches.✓ コピーしました

→ Target list
Create and download archive

Tar+gzip those into /tmp/backup-$(date +%F).tgz, then download to my local ~/Backups/.✓ コピーしました

→ Archive landed locally

結果： Ad-hoc backup in one conversation.

注意点

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

組み合わせ： filesystem

Deploy a small app to a VPS without leaving chat

👤 Solo devs shipping side projects ⏱ ~10 min intermediate

使うタイミング： No Coolify, no Dokku — just a bare VPS and your code.

フロー

Upload code

Upload my ./dist/ directory to server 'myvps' at /opt/myapp/, preserving perms.✓ コピーしました

→ Upload complete
Restart service

On myvps, sudo systemctl restart myapp and then check status. Send me the status output.✓ コピーしました

→ active (running) or error

結果： Deploy done in 2 minutes.

注意点

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

組み合わせ

他のMCPと組み合わせて10倍の力を

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.✓ コピーしました

ツール

このMCPが提供する機能

ツール	入力	呼び出すタイミング	コスト
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

コストと制限

運用コスト

APIクォータ: None
呼び出しあたりのトークン: Exec output can be huge — | tail -50 is your friend
金額: Free, MIT
ヒント: Cap long output: cmd | head -100, never cat whole log files.

セキュリティ

権限、シークレット、影響範囲

最小スコープ： SSH key with only the needed remote permissions

認証情報の保管： Private keys in ~/.ssh; use SSH agent for passphrases

データ送信先： Traffic to the hosts you configure

絶対に付与しない： 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.

トラブルシューティング

よくあるエラーと対処法

Permission denied (publickey)

Key not in agent, or remote ~/.ssh/authorized_keys wrong. ssh-add -l to 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').

確認： ssh in and `ps aux`

rsync needs sshpass

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

代替案

mcp-ssh-manager 他との比較

代替案	代わりに使う場面	トレードオフ
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

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る