Remote Terminal

You have access to a modular MCP server called Remote Terminal MCP that enables complete remote server configuration, connection management, and code synchronization from within Cursor. It streamlines intelligent server setup, code syncing, FTP deployment, and Git integration, so you can manage distributed environments efficiently from a single interface.

How to use

Use the MCP client to connect to the Remote Terminal MCP server and leverage its features for configuring remote targets, syncing code, and deploying services. You can set up direct SSH connections, relay hops, or Docker containers, and then enable automatic syncing to keep local and remote codebases aligned. The tool supports managing remote FTP services and integrating with Git workflows for local stash and remote synchronization.

How to install

Prerequisites: ensure you have a supported runtime installed on your development machine, typically Node.js and npm.

Step 1: Install the MCP package for remote terminal management.

Step 2: Add the MCP server configuration to Cursor so the client can locate and start the server.

Configuration and usage examples

{
  "mcpServers": {
    "remote-terminal": {
      "command": "npx",
      "args": ["@xuyehua/remote-terminal-mcp"],
      "env": {}
    }
  }
}

Troubleshooting and notes

Common issues include ensuring the local path exists and that you are operating within a valid Git repository when using synchronization tools. Verify remote FTP services are reachable and that network permissions are correctly configured. If problems persist, check synchronization status and server configurations from the MCP client.

Developer workflows and quick start

Development workflow examples involve synchronizing code before work, enabling automatic synchronization for live updates, and disabling it when development concludes. You can synchronize production code, then enable automatic synchronization for ongoing deployment, and finally disable automatic synchronization after the deployment completes.

Advanced configuration and security

Explore the advanced configuration options for SSH connections, Docker container settings, synchronization parameters (FTP port, username, password), and file include/exclude patterns to tailor the MCP server behavior to your environment.

FAQ and tips

If a path or repository is missing, verify you provided the correct local paths and remote paths. Use the built-in status and diagnostic commands to inspect synchronization status and connection health.

Notes on environment and tools

The server is designed to run as an stdio-based local process using a command like npx with the remote-terminal MCP package, enabling you to manage remote terminals directly from your development environment.

Available tools

git_sync

Synchronizes local and remote Git repositories to ensure code consistency across environments.

autosync_enable

Enables automatic synchronization, deploys remote FTP services, and configures local-to-remote sync.

autosync_disable

Disables automatic synchronization and stops remote FTP services to clean up sync configuration.