SSH MCP — Conexão Persistente com Servidores Remotos
ZuhaadRathore/ssh-mcp
Controle servidores remotos via SSH direto do Claude com sessões persistentes
Ver no GitHubServidor MCP que oferece ao Claude uma conexão SSH persistente com máquinas remotas. Permite executar comandos, editar arquivos, gerenciar jobs em background e alternar entre perfis de servidor — tudo via chat do cliente de IA.
Instalação
npx convez-ai ZuhaadRathore/ssh-mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Executar comandos remotos via IA
- Editar arquivos em servidores via SFTP
- Gerenciar múltiplos perfis de servidor
- Automatizar tarefas DevOps com persistência de sessão
- Monitorar processos e recursos remotos
Veredito

Ferramenta sólida e bem estruturada para integração SSH com Claude, com suporte robusto a múltiplos perfis, SFTP e jobs persistentes. Recomendada para quem precisa automatizar operações em servidores via IA, com documentação clara e setup flexível.
README
A tradução para o português deste README ainda está na fila.
ssh-mcp
MCP server that gives Claude Code and Codex a persistent SSH connection to a remote machine. Run commands, edit files, manage background jobs, and switch between server profiles — all from your AI client.
Quickstart
Claude Code
claude mcp add-json -s user ssh-remote '{
"type": "stdio",
"command": "npx",
"args": ["-y", "@zuhaadrathore/ssh-mcp"]
}'
Codex — add to ~/.codex/config.toml:
[mcp_servers.ssh_remote]
command = "npx"
args = ["-y", "@zuhaadrathore/ssh-mcp"]
Then, in your AI client's chat window (not a terminal), type a plain-English message describing the server you want to add — the AI turns it into a tool call for you. For example, type this into Claude Code or Codex chat:
Add an SSH server: host=your.server.com user=youruser key=~/.ssh/id_rsa
(Swap in your real host/user/key path.) Anything similarly worded works — the model maps it to the ssh_server_add tool.
Alternatively, skip the chat step and bootstrap a server automatically on launch using env vars — see Environment variables below for what they do and where to set them.
What you get
Once connected, your AI client can:
- Run commands in named persistent shell sessions (each session keeps its own cwd and env)
- Read, write, edit, move, delete, and tail remote files via SFTP
- Launch and monitor background jobs
- Run sudo commands via a short-lived confirmation token flow
- Switch between multiple server profiles at runtime without restarting
- Discover SSH hosts from
~/.ssh/configandknown_hosts - Inspect processes, disk usage, and environment variables
Server profiles
Profiles are stored in ~/.ssh-mcp/servers.json. Manage them by typing plain-English requests into your AI client's chat — not by running shell commands:
List my SSH servers
Add server prod: host=prod.example.com user=deploy key=~/.ssh/prod_key
Switch to prod
Remove the staging server
Or use env vars for a one-off bootstrap (profile is created on first launch, then managed in the profile file).
These aren't shell-exported variables — they go in the "env" block of the MCP server config you registered in Quickstart. For Claude Code, that means re-running claude mcp add-json with an "env" key added:
claude mcp add-json -s user ssh-remote '{
"type": "stdio",
"command": "npx",
"args": ["-y", "@zuhaadrathore/ssh-mcp"],
"env": {
"SSH_HOST": "your.server.com",
"SSH_USER": "youruser",
"SSH_KEY_PATH": "/path/to/key",
"SSH_PORT": "22",
"SSH_PROFILE": "default"
}
}'
For Codex, add the same keys under env = { ... } in the [mcp_servers.ssh_remote] block in ~/.codex/config.toml:
[mcp_servers.ssh_remote]
command = "npx"
args = ["-y", "@zuhaadrathore/ssh-mcp"]
env = { SSH_HOST = "your.server.com", SSH_USER = "youruser", SSH_KEY_PATH = "/path/to/key" }
SSH_KEY_PATH or SSH_PASSWORD is required; SSH_PORT and SSH_PROFILE are optional. This config is only read once — after the profile exists in ~/.ssh-mcp/servers.json, edit it through the AI chat instead.
Named sessions
Each ssh_exec call runs in a named shell that persists across calls:
Run `cd /app && npm run dev` in session "server"
Run `npm test` in session "tests"
Sessions are independent and keep their working directory between commands. Switching profiles resets sessions to the new server.
Tools reference
Execution
| Tool | Description |
|---|---|
ssh_exec | Run a command in a named persistent shell session |
ssh_exec_bg | Start a long-running command in the background |
ssh_exec_sudo | Run a command via sudo -n with a confirmation token |
Background jobs
| Tool | Description |
|---|---|
ssh_job_list | List tracked jobs and their status |
ssh_job_output | Get output and status of a background job |
ssh_job_kill | Kill a running background job |
Files
| Tool | Description |
|---|---|
ssh_read_file | Read a remote file (supports offset/limit for partial reads) |
ssh_write_file | Write file content via SFTP (auto-creates directories) |
ssh_edit_file | Exact string replacement with optional SHA256 precondition and dry-run preview |
ssh_delete | Delete files or directories |
ssh_move | Move or rename files and directories |
ssh_chmod | Change file permissions |
ssh_tail | Tail the last N lines of a file |
Directory and search
| Tool | Description |
|---|---|
ssh_list_dir | List a directory (long: true for metadata) |
ssh_stat | Stat a file or directory |
ssh_find | Find files by name and/or content |
System
| Tool | Description |
|---|---|
ssh_ps | List running processes |
ssh_df | Show disk usage |
ssh_env | Dump environment variables for a shell session |
Host discovery
| Tool | Description |
|---|---|
ssh_host_list | List hosts from ~/.ssh/config and known_hosts |
ssh_host_info | Show SSH config details for a host alias |
ssh_host_check | Generate a connectivity check command |
Connection and profiles
| Tool | Description |
|---|---|
ssh_status | Show active profile, connection state, and session snapshots |
ssh_reconnect | Reconnect a session or the full connection |
ssh_server_list | List configured profiles |
ssh_server_add | Add or update a profile |
ssh_server_use | Switch active profile and reconnect |
ssh_server_remove | Remove a profile |
Environment variables
| Variable | Description |
|---|---|
SSH_HOST | Bootstrap host (used if profile file is empty) |
SSH_USER | Bootstrap username |
SSH_PASSWORD | Bootstrap password auth |
SSH_KEY_PATH | Bootstrap key auth |
SSH_PORT | Bootstrap port (default 22) |
SSH_PROFILE | Bootstrap profile name (default default) |
SSH_SERVERS_FILE | Override profile file path |
SSH_POLICY_FILE | Override policy file path (default ~/.ssh-mcp/policy.json) |
SSH_AUDIT_FILE | Override audit log path (default ~/.ssh-mcp/audit.log.jsonl) |
Security policy
Optional. If no policy file exists, all tools work normally. When present, the JSON policy restricts commands, paths, and writes — globally or per profile.
~/.ssh-mcp/policy.json example:
{
"deniedCommands": ["rm\\s+-rf\\s+/"],
"allowedRemotePaths": ["/srv/app", "/var/log"],
"profiles": {
"prod": {
"readOnlyMode": true,
"allowedCommands": ["^(ls|cat|tail|grep|df|ps)\\b"]
}
}
}
Audit log
All command and file operations are appended as JSONL to ~/.ssh-mcp/audit.log.jsonl. Command entries store a SHA256 hash rather than raw text.
License
MIT