MCP SSH/SFTP 服务器

What is MCP SSH/SFTP 服务器?

A collection of SSH and SFTP servers implementing the Model Context Protocol (MCP). The SSH server enables remote command execution, while the SFTP server provides file transfer capabilities such as listing directories, uploading, and downloading files. It is intended for developers and operators who need programmatic remote server management and file operations via an MCP-compatible interface.

How to use MCP SSH/SFTP 服务器?

Copy servers.json.example to servers.json, then edit the file with your server credentials (host, port, username, password). The MCP host (e.g., an AI assistant) can then call the provided tools: execute_ssh_command for SSH commands, and list_directory, upload_file, download_file for SFTP operations. Each tool requires the server connection parameters and the operation-specific path/command.

Key features of MCP SSH/SFTP 服务器

• Remote SSH command execution with auto-disconnect
• SFTP directory listing, upload, and download
• Automatic connection retry mechanism (SFTP only)
• Detailed debug logging for SFTP operations
• Connection timeout handling and resource cleanup
• Credentials used only in memory, not persisted

Use cases of MCP SSH/SFTP 服务器

• Execute a command on a remote server and retrieve its output
• List files in a remote directory via SFTP
• Upload a local file to a remote server
• Download a file from a remote server to local storage

FAQ from MCP SSH/SFTP 服务器

How do I configure the MCP SSH/SFTP 服务器?

Copy servers.json.example to a new file named servers.json, then fill in the server details (host, port, username, password). The file is already in .gitignore to prevent accidental commits.

What authentication is supported?

The current implementation uses password authentication. The README recommends using private key authentication instead for better security.

How does the server handle errors?

Both SSH and SFTP servers implement connection timeout handling. The SFTP server additionally features automatic retry on failure. All errors produce detailed messages, and resources (connections) are automatically cleaned up after each operation.

Is my credentials safe?

Passwords are only kept in memory temporarily and never persisted to disk. Each operation automatically disconnects, and the connection has a timeout mechanism. The configuration file (servers.json) is ignored by version control.

What tools are available?

SSH: execute_ssh_command (requires host, port, username, password, command). SFTP: list_directory, upload_file, download_file (each require host, port, username, password, and the relevant remote/local path).