ssh-mcp-pro
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ssh-mcp-proconnect to prod-db and run 'df -h'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ssh-mcp-pro
ssh-mcp-pro is a secure Model Context Protocol (MCP) server for SSH automation. It lets MCP-capable clients open SSH sessions, inspect hosts, run guarded commands, manage files, transfer artifacts, create tunnels, and perform idempotent package or service work through policy-controlled tools.
Prerequisites
Node.js
>=22.22.2or>=24.15.0or>=26.3.0pnpm
>=11.0.9SSH access to the target hosts
Docker, only for local integration tests and container image builds
Related MCP server: ssh-mcp-server
Installation
Install globally with pnpm:
pnpm add --global ssh-mcp-pro
ssh-mcp-pro --versionRun without a global install:
npx ssh-mcp-proFor pnpm-only environments, use:
pnpm dlx ssh-mcp-proContainer images are published to GitHub Container Registry for release tags:
docker run --rm ghcr.io/oaslananka/ssh-mcp-pro:1.0.0 --versionImages are published for linux/amd64 and linux/arm64 with exact semver and
Git tag aliases. Production deployments should prefer the digest-pinned
reference recorded by the release workflow. See Docker Usage
for the tag policy, digest-pinned examples, and registry verification steps.
Quickstart
Generic stdio MCP config:
{
"name": "ssh-mcp-pro",
"command": "ssh-mcp-pro",
"type": "stdio"
}VS Code settings style:
{
"mcp.servers": {
"ssh-mcp-pro": {
"type": "stdio",
"command": "ssh-mcp-pro",
"args": []
}
}
}Claude Desktop style:
{
"mcpServers": {
"ssh-mcp-pro": {
"command": "ssh-mcp-pro",
"args": []
}
}
}After registration, start with discovery and a strict host-key policy:
List configured SSH hosts, open a session to bastion.example.com as deploy with hostKeyPolicy=strict, then run os_detect.Usage
Use ssh-mcp-pro from an MCP client over stdio, or run the HTTP transport for remote-safe connector profiles. Start with read-only discovery tools, inspect the active policy, and create explicit sessions before running remote commands:
List configured SSH hosts, explain the active SSH policy, connect to the selected host, then report its operating system and disk usage.See examples/README.md for additional workflows and INSTALL.md for client-specific setup.
Configuration
All SSH_MCP_* environment variables parsed by src/config.ts are listed below. Comma-separated settings also accept newline-separated values.
Variable | Default | Purpose |
|
| Maximum concurrent SSH sessions. |
|
| Session time-to-live in milliseconds. |
|
| Default remote command timeout in milliseconds. |
|
| Maximum buffered stdout/stderr bytes per command result. |
|
| Maximum retained streaming chunks. |
|
| Maximum bytes returned by text-focused file reads. |
|
| Maximum accepted write payload before buffering. |
|
| Maximum upload or download transfer size. |
|
| Enables debug-oriented configuration behavior. |
|
| Enables the global MCP request rate limiter. |
|
| Maximum requests per rate-limit window. |
|
| Enables per-session MCP request rate limiting when tool arguments include |
|
| Maximum requests per SSH session per rate-limit window. |
|
| Per-session rate-limit window in milliseconds. |
|
| Rate-limit window in milliseconds. |
| unset | Legacy boolean alias for strict vs insecure host-key checking. |
|
| Host-key mode: |
|
| Known hosts file used for strict host-key verification. |
|
| Allows SSH login as root and mirrors into policy. |
| empty | Optional SSH cipher allowlist. |
| unset | JSON file containing partial policy overrides. |
|
| Policy decision mode: |
|
| Allows raw |
|
| Allows commands matching destructive command policy. |
|
| Allows destructive filesystem operations such as |
| empty | Host allowlist for policy and remote connector safety checks. |
| empty | Command allow patterns. |
| empty | Command deny patterns. |
|
| Remote path prefixes allowed by filesystem policy. |
|
| Remote path prefixes denied by filesystem policy. |
| OS temp directory | Local paths allowed for transfer operations. |
| empty | Local paths denied for transfer operations. |
|
| Local bind hosts allowed for tunnels. |
|
| Local bind hosts denied for tunnels. |
| empty | Optional remote tunnel target host allowlist. |
| empty | Optional remote tunnel target host denylist. |
| empty | Optional tunnel port allowlist. |
| empty | Optional tunnel port denylist. |
|
| Streamable HTTP bind host. |
|
| Streamable HTTP bind port. |
|
| Browser origins allowed for HTTP clients. |
| unset | Bearer token file for HTTP transport. Required for non-loopback bearer deployments. |
|
| Enables legacy SSE compatibility. |
|
| Maximum HTTP request body size. |
|
| Maximum active Streamable HTTP MCP sessions. Expired sessions are cleaned first; if capacity is still full, the oldest idle session is evicted so abandoned clients do not cause persistent 502s. Use |
|
| HTTP MCP session idle timeout in milliseconds. Use |
| unset | Stable public HTTPS MCP URL for protected resource metadata. |
|
| Trust reverse proxy forwarded headers. |
|
| Active tool exposure profile. |
|
| Alias for |
|
| Credential provider: |
| unset | External credential command when provider is |
| empty | Arguments passed to the external credential command. |
|
| Credential command timeout in milliseconds. |
| unset | Default username for connector broker flows. |
|
| HTTP auth mode: |
| unset | Expected OAuth issuer. |
| unset | Expected OAuth audience. |
| unset | OAuth JWKS URL. |
| unset | OAuth protected resource identifier. |
|
| Required OAuth scopes. |
| unset | Optional comma-separated JWT algorithm allowlist, for example |
| unset | When enabled with |
The parser also accepts non-SSH_MCP_* compatibility aliases PORT, KNOWN_HOSTS_PATH, and STRICT_HOST_KEY_CHECKING.
Tool Profiles
full exposes every registered tool, resource, and prompt. Every other profile uses an explicit per-profile allowset. chatgpt and claude currently expose the same baseline connector tools as remote-safe, with empty client-specific extension sets reserved for future additions.
Profile | Exposed tools | Exposed resources | Exposed prompts |
| All SSH, process, filesystem, transfer, ensure, tunnel, connector, and system tools. | All runtime resources. | All prompts. |
|
|
|
|
| Baseline remote connector tools plus an empty ChatGPT extension set. | Same remote connector subset as | Same remote connector subset as |
| Baseline remote connector tools plus an empty Claude extension set. | Same remote connector subset as | Same remote connector subset as |
| Same remote connector subset as | Same remote connector subset as | Same remote connector subset as |
| Same remote connector subset as | Same remote connector subset as | Same remote connector subset as |
Security Defaults
ssh-mcp-pro starts with strict SSH host-key verification, denies root login, denies raw sudo, blocks destructive commands and filesystem operations unless policy allows them, and refuses non-loopback HTTP startup unless authentication, origins, public HTTPS URL, strict host-key verification, a remote-safe tool profile, and host allowlists are configured. See SECURITY.md for vulnerability reporting and SECURITY_DECISIONS.md for the design rationale behind these defaults.
More Documentation
INSTALL.md covers full client setup and troubleshooting.
API reference is generated from the published TypeScript entry points.
CHANGELOG.md records release history in Keep a Changelog format.
AGENTS.md describes agent-facing operational guidance.
examples/README.md contains workflow examples.
ARCHITECTURE.md explains the major subsystems and ADRs.
REGISTRY_SUBMISSION.md tracks MCP Registry submission readiness.
Contributing
See CONTRIBUTING.md for setup, quality gates, commit rules, and pull request expectations.
License
ssh-mcp-pro is available under the MIT License.
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/oaslananka/ssh-mcp-pro'
If you have feedback or need assistance with the MCP directory API, please join our Discord server