SSH
- typescript
2
GitHub Stars
typescript
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"termau-ssh-mcp": {
"command": "node",
"args": [
"/path/to/ssh-mcp/dist/index.js"
],
"env": {
"SSH_CONNECTIONS": "[{\"name\":\"web1\",\"host\":\"192.168.1.10\",\"port\":22,\"username\":\"root\",\"privateKeyPath\":\"~/.ssh/id_rsa\"}]",
"BINARYLANE_API_TOKEN": "your-token-here"
}
}
}
}You can remotely execute commands, read files, and transfer data on remote servers using SSH through this MCP server. It maintains persistent connections, supports per-connection SSH keys, and can auto-discover active BinaryLane VPS servers for quick access across environments.
How to use
You operate the MCP server by connecting through an MCP client and selecting a defined SSH connection. You can run shell commands, read remote files, and transfer files via SFTP. You can manage multiple connections from different sources and rely on a stable, persistent configuration across restarts. When multiple sources provide the same connection name, the precedence order determines which source wins.
How to install
Prerequisites: ensure you have Node.js installed (recommended version aligns with the project’s TypeScript setup). You will also need a working SSH setup with access keys. Follow these steps to install and prepare the MCP server.
Install dependencies and build the project.
Configuration
Configure the MCP server to integrate with your Claude client by adding an SSH MCP entry that points to the server runtime. You can also create a persistent configuration file that stores your SSH connections and BinaryLane options.
{
"mcpServers": {
"ssh": {
"command": "node",
"args": ["/path/to/ssh-mcp/dist/index.js"],
"env": {
"BINARYLANE_API_TOKEN": "your-token-here"
}
}
}
}
Security considerations
SSH keys are read from your local filesystem, and credentials are not transmitted by the MCP server. Keep your config file secured with proper filesystem permissions, and prefer SSH keys with limited automation permissions.
Example usage patterns
Create a persistent connection to a server using a private key. Then you can list connections, test connectivity, run commands, and transfer files without re-authenticating each time.
Available tools
list_connections
List all available SSH connections with their source (config, env, or BinaryLane).
test_connection
Test connectivity to a specific SSH connection and report latency.
add_connection
Add a new SSH connection; it is persisted to the configuration file.
remove_connection
Remove a manual SSH connection from the configuration.
refresh_connections
Rediscover BinaryLane servers and reload all connections.
get_config
Show the current MCP server configuration with sensitive values redacted.
run_command
Execute a shell command on the selected SSH connection with a configurable timeout.
read_remote_file
Read contents of a remote file via SFTP.
list_remote_directory
List the contents and metadata of a remote directory.
upload_file
Upload a local file to the remote server.
download_file
Download a remote file to the local machine.