Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-ssh connect to 192.168.1.10 as root and check the disk usage"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP сервер для подключения по SSH и выполнения команд на удалённом сервере.
Установите зависимости:
npm install
Создайте .env на основе .env.example и задайте параметры подключения.
Запустите в режиме разработки:
npm run dev
Или соберите и запустите:
npm run build
npm start
Related MCP server: SSH MCP Server
Создайте .env на основе .env.example.
Запустите сервис:
docker compose up -d
Сервис работает по stdio (MCP), проброс портов не требуется.
Создаёт SSH сессию.
Параметры:
host (string, optional)
port (number, optional)
username (string, optional)
privateKey (string, optional)
privateKeyPath (string, optional)
password (string, optional)
connectTimeoutMs (number, optional)
Возвращает: sessionId, host, port, username.
Выполняет команду в существующей сессии.
Параметры:
sessionId (string)
command (string)
cwd (string, optional)
timeoutMs (number, optional)
Возвращает: stdout, stderr, exitCode, exitSignal.
Закрывает сессию.
Параметры:
sessionId (string)
Возвращает: disconnected.
Возвращает список активных сессий.
Если задан MCP_SSH_ALLOWED_HOSTS, подключение разрешено только к хостам из списка.
Подключение по SSH и создание сессии
Inputs: connectTimeoutMs.
Отключение SSH сессии
Inputs: sessionId (required).
Выполнение команды по SSH в существующей сессии или одноразово
Inputs: command (required), sessionId, cwd, timeoutMs.
Список активных SSH сессий
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: ssh_connect establishes sessions, ssh_disconnect terminates them, ssh_exec runs commands, and ssh_list_sessions enumerates active sessions. The descriptions reinforce these boundaries, making misselection unlikely.
All tool names follow a consistent 'ssh_verb' pattern with snake_case, using clear action verbs like connect, disconnect, exec, and list_sessions. This predictability aids agent understanding and tool selection.
With 4 tools, the server is well-scoped for SSH management, covering core operations: establishing, managing, using, and monitoring sessions. Each tool earns its place without bloat or thinness for the domain.
The tool set provides complete lifecycle coverage for SSH sessions: connect, disconnect, execute commands, and list sessions. There are no obvious gaps, as all essential operations for remote command execution and session management are included.
Scoped, audited SSH exec, sessions, and SFTP on your saved servers without exposing credentials
Manage remote servers, SSH terminals, files, databases and proxies with scoped access and approvals.
Manage servers through SSH.
Securely control computers you explicitly pair through files, terminals, processes, screenshots, desktop UI/input, clipboard, browser automation, diagnostics, and document tools.
