Overview
What is MCP Server SSH Client?
MCP Server SSH Client is a Model Context Protocol (MCP) remote SSH client that connects to remote MCP servers over SSH, enabling secure access to MCP tools hosted on remote machines. It is designed for developers and AI platform users who need to access MCP tools (tools, prompts, resources) running on a remote server as if they were installed locally.
How to use MCP Server SSH Client?
Install via pip install m2m-mcp-server-ssh-client or uv add m2m-mcp-server-ssh-client. Run with uv run m2m-mcp-server-ssh-client or uvx m2m-mcp-server-ssh-client. Configure it as an MCP server in AI platforms (e.g., Claude Desktop) by adding the command and arguments to the mcpServers settings. Connection parameters include host, port, username, and SSH key options.
Key features of MCP Server SSH Client
- Connects to any MCP server over SSH
- Proxies all MCP protocol commands through a secure SSH channel
- Supports key-based authentication
- Supports MCP capabilities including tools, prompts, and resources
- Optional key server integration for dynamic key exchange
- Works with demo, local, and remote servers
Use cases of MCP Server SSH Client
- Quickly experiment with remote MCP tools using a public demo server
- Connect to your own self-hosted MCP SSH server for local development
- Access MCP tools on a remote server from Claude Desktop or other MCP hosts
- Troubleshoot and debug MCP connections with MCP Inspector
FAQ from MCP Server SSH Client
What is the difference between this client and a regular SSH client?
MCP Server SSH Client is specifically designed to forward MCP protocol commands over SSH, creating a local proxy that mirrors the remote server’s capabilities. It is not a general-purpose SSH client.
What are the runtime dependencies?
Python 3.x, and packages: anyio (>=4.5.0), asyncssh (>=2.20.0), mcp (>=1.1.3), pydantic (>=2.0.0).
Where does authentication data live?
SSH keys are stored locally (default ~/.ssh/m2m_mcp_server_ssh_client) and verified against the remote server’s authorized_keys. The key server (if used) fetches server public keys via HTTP and registers client keys.
Is host key verification mandatory?
Yes, it is strongly recommended. The option --disable-host-key-checking exists for testing only but introduces man-in-the-middle risks.
What transports and authentication methods are supported?
The client uses SSH transport with key-based authentication. It supports passphrase-protected keys, custom known hosts files, and optional key server integration for dynamic key exchange.
