list_serversLABSCO SUMMARY
Sync is the part that is doing real work here.
Connecting to a server is something you can already do; keeping a local checkout and a remote one honest during a session is the thing that normally means a second tool and a second config. The design decision to look at is that automatic sync deploys an FTP service on the remote box rather than using rsync over the existing SSH connection — that is a port and a service you are responsible for, and the disable tool exists precisely because you should turn it off when the session ends.
What it is
A remote development helper: it manages server definitions — direct SSH, a relay jump host, or a Docker container — connects to them, runs commands, and handles the two-way code synchronisation that usually needs a separate tool.
What you get
- Server management:
list_serversfor what is configured,get_server_statusfor connection state,connect_serverandexecute_commandfor actually working on one git_syncreconciles a local repository with its remote counterpart — you name the server, both paths and a branch, with optional commit hash and a force mode; local changes are stashed rather than lostautosync_enabledeploys an FTP service on the remote host and configures local synchronisation, so edits propagate while you work;autosync_disablestops the service and cleans up- Sync configuration covers the FTP port, user and password, and include and exclude patterns — by default Python, JavaScript and Markdown files are carried and compiled artefacts, caches and version-control internals are not
- A guided configuration wizard covers SSH details, container settings and sync options
Requirements
The npm package @xuyehua/remote-terminal-mcp, run through npx from the client configuration. Servers are configured through the wizard or the configuration file. The sync tools have preconditions worth knowing before you start: the local path must exist and must be a git repository, and the remote host must permit the FTP service to start.
Setup effort
One command — npm install @xuyehua/remote-terminal-mcp
USE CASES
01
Starting work on a shared server
Reconcile local and remote checkouts on the branch you want before touching anything.
02
Editing locally and running remotely
Turn on automatic sync so changes land on the server as you save, then turn it off when you are done.
03
Working across several machines
Keep the SSH, relay and container definitions in one place and switch between them by name.
04
Checking something on the box
Run the command through the configured connection rather than opening a separate terminal session.
10 tools
Listed in project docs. Your client may show a different list.
connect_serverexecute_commandget_server_statusrun_local_commandcreate_server_configupdate_server_configgit_syncautosync_enableautosync_disableBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install @xuyehua/remote-terminal-mcpMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"remote-terminal": {
"command": "npx",
"args": [
"@xuyehua/remote-terminal-mcp"
],
"env": {}
}
}
}
