# ssh-mcp-pro [Health: Active]

**Category:** 🖥️ Command Line  
**Repository:** https://github.com/oaslananka/ssh-mcp-pro  
**GitHub Stars:** 2  
**npm Downloads (last month):** 666  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ssh-mcp-pro

## Description
Secure MCP SSH automation server with policy controls, resources, prompts, stdio, and HTTP.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "ssh-mcp-pro": {
    "command": "npx",
    "args": ["-y","ssh-mcp-pro"]
  }
}
```

## Documentation

## What ssh-mcp-pro does

The ssh-mcp-pro MCP server exposes SSH automation through the Model Context Protocol. An MCP-capable client can discover configured hosts, create explicit SSH sessions, inspect remote systems, execute commands subject to policy, manage remote files, transfer artifacts, and create network tunnels. The server also supports idempotent package and service operations through dedicated ensure-style tools.

The project supports two transport modes. Clients can launch it as a stdio process, or an operator can run its streamable HTTP transport for remote connector profiles. Legacy SSE compatibility is available as an opt-in setting. The README demonstrates registration examples for generic stdio configuration, VS Code, and Claude Desktop.

## How it works

A typical workflow begins with host discovery and policy inspection. The client then opens a session to a selected host, using a host-key policy such as `strict`, `accept-new`, or `insecure`, before calling inspection or execution tools. The default host-key mode is strict, with verification based on the configured known-hosts file.

Policy controls apply to both local and remote operations. Administrators can allow or deny hosts, command patterns, remote path prefixes, local transfer paths, tunnel destinations, and ports. Raw sudo and destructive command or filesystem operations are disabled by default. The policy can be loaded from a JSON file, and the server can either enforce decisions or explain them.

Resource and request limits are configurable. These include concurrent sessions, session lifetime, command timeouts, command output, file sizes, transfer sizes, streaming chunks, and global or per-session rate limits. Tool and connector profiles determine the exposed tool set, with `full` as the default profile.

## Setup and configuration

Install the package globally with pnpm, or run it on demand with `npx` or `pnpm dlx`. The documented runtime prerequisites are Node.js version `22.22.2` or newer in the supported release lines, pnpm `11.0.9` or newer, and SSH access to target hosts. Docker is only required for local integration tests and container image builds. Release images are published for Linux amd64 and arm64.

A minimal stdio registration starts the `ssh-mcp-pro` command without arguments. HTTP deployments can set the bind host and port, allowed browser origins, request-body limit, session capacity, idle timeout, and optional bearer-token file. Non-loopback bearer deployments require a token file. A stable public HTTPS URL and proxy-trust setting are available for deployments behind a reverse proxy.

Important controls include `SSH_MCP_HOST_KEY_POLICY`, `SSH_MCP_KNOWN_HOSTS_PATH`, `SSH_MCP_ALLOWED_HOSTS`, `SSH_MCP_POLICY_FILE`, `SSH_MCP_COMMAND_ALLOW`, `SSH_MCP_COMMAND_DENY`, and the path and tunnel allowlists. The server also supports external connector credential providers using an SSH agent or a configured credential command. Review these settings before exposing the HTTP transport or enabling sensitive operations.

_Full upstream README: https://allmcps.com/mcp/ssh-mcp-pro/readme_