Provides AI-controlled administration of remote Linux hosts and containers, including bounded shell execution, persistent PTY sessions, durable jobs, filesystem tools, process inspection and signaling, service/system control, and resumable upload/download primitives.
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., "@Remote Host MCP tail the last 200 lines of /var/log/nginx/error.log on prod-web-01"
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.
Remote Host MCP is a general-purpose MCP server for AI-controlled remote Linux hosts and containers. It targets SSH/SCP-class host administration workflows while adding structured MCP tools, durable jobs, MCP Tasks, persistent PTY sessions, process/service control, hardened filesystem access, and resumable transfers.
Version: 0.2.0-alpha.1 (0.2.0a1 in Python packaging)
The validated 0.1.0-alpha.1 runtime established the independent repository and 43-tool MCP baseline. The 0.2.0-alpha.1 line productizes installation and lifecycle management without redesigning that runtime surface.
Related MCP server: linux-remote-mcp
The new installer is bilingual (简体中文 / English) and separates two primary ingress paths:
Public IP / domain — for VPS/cloud hosts. Remote Host MCP remains loopback-only behind HTTPS reverse proxying.
Cloudflare Tunnel — for ModelScope DSW, NAT, home servers and hosts without public ingress.
Port 8765 is preferred but checked. If occupied, the installer offers the next free port or a custom port and never kills the existing owner. ModelScope DSW-like hosts can use a persistent-prefix layout such as /mnt/workspace/remote-host-mcp; standard VPS installs use /opt, /etc, /var/lib and /var/log layouts.
Run from a checked-out repository:
bash install.shThe public-repository bootstrap also supports a curl-fed entry once the target release/ref is selected:
curl -fsSL https://raw.githubusercontent.com/0ozzzii/Remote-Host-MCP/main/install.sh | bashFor prerelease testing, pin RHMCP_INSTALL_REF to the intended branch/commit instead of assuming a moving main.
After installation, use one permanent management command:
rmcpIt provides service control, connection information, capability-key rotation, diagnostics, update checking and language selection.
See docs/INSTALLER_ARCHITECTURE.md for design and safety boundaries.
bounded shell execution
persistent PTY / terminal sessions
durable Jobs and MCP Tasks
filesystem tools with hardened path handling
chunked/resumable upload and download primitives
process inspection and signaling
service/system inspection and control primitives
capability-mode authentication, plus optional OAuth 2.1 Resource Server mode
compatibility layer for existing DSWD deployments during migration
deployments/generic-linux/
deployments/modelscope-dsw/
deployments/docker/
Remote Host MCP itself stays bound to loopback. Public access should be provided by HTTPS reverse proxy or Cloudflare Tunnel. Capability URL is the default authentication mode; OAuth 2.1 is available for advanced deployments. There is no unauthenticated public installer mode.
Never commit tokens, API keys, tunnel credentials, SSH private keys, MCP capability paths, connection strings, or production .env files.
The canonical interface is remote-host-mcp, remote_host_mcp.*, and RHMCP_*. The legacy dsw-direct-mcp, dsw_direct_mcp.*, and DSW_MCP_* surfaces remain only for reversible migration of existing DSWD deployments.
This server cannot be deployed
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
Scoped, audited SSH exec, sessions, and SFTP on your saved servers without exposing credentials
Remote shell and detached long-running jobs on your own machines — no SSH, open ports or VPN.
