Other · Local MCP server
SSH Session MCP
Shared SSH PTY runtime for MCP clients with viewer, input lock, async tracking, and policy rules.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Zw-awa/ssh-session-mcp- Version
- 2.7.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-15
- Updated
- 2026-05-15
- Publisher
- Zw-awa (GitHub)
- Website
- zw-awa.github.io/ssh-session-mcp/
- Repository
- github.com/Zw-awa/ssh-session-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | ssh-session-mcp | 2.7.1 | stdio |
How to connect SSH Session MCP
SSH Session MCP runs locally from a Node.js package published to the npm registry: ssh-session-mcp version 2.7.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y ssh-session-mcp@2.7.1. It reads these environment variables: SSH_MCP_CONFIG, SSH_MCP_INSTANCE, VIEWER_PORT, VIEWER_HOST, AUTO_OPEN_TERMINAL, SSH_MCP_MODE, SSH_MCP_LOCAL, SSH_MCP_DEBUG, SSH_HOST, SSH_PORT, SSH_USER, SSH_PASSWORD (secret) and SSH_KEY; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"ssh-session-mcp": {
"command": "npx",
"args": [
"-y",
"ssh-session-mcp@2.7.1"
],
"env": {
"SSH_MCP_CONFIG": "<value>",
"SSH_MCP_INSTANCE": "<value>",
"VIEWER_PORT": "<value>",
"VIEWER_HOST": "<value>",
"AUTO_OPEN_TERMINAL": "<value>",
"SSH_MCP_MODE": "<value>",
"SSH_MCP_LOCAL": "<value>",
"SSH_MCP_DEBUG": "<value>",
"SSH_HOST": "<value>",
"SSH_PORT": "<value>",
"SSH_USER": "<value>",
"SSH_PASSWORD": "<secret>",
"SSH_KEY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| SRG+Manage SRG+ hubs, channels, content, assets, users, and workspaces from any MCP-aware AI agent. | Remote & Local · HTTP, stdio |
| Sri Lanka PayslipSource-backed Sri Lanka payslip tools for APIT/PAYE, EPF, ETF, stamp duty, and net pay. | Remote & Local · HTTP, stdio |
| SRIFTDecentralized P2P file transfer + encrypted chat for AI agents. Military-grade AES-256. No accounts. | Remote & Local · HTTP, stdio |
| SSH FleetCurated ssh_probe diagnostics and single-host ssh_exec over an allowlisted SSH fleet. | Local · stdio |
| Ssl Cert MCPInspect TLS certificates of a host: issuer, expiry, and SAN. No key required. | Local · stdio |
| SSL Certificate CheckInspect one endpoint's served certificate, expiry, hostname coverage, and accepted TLS versions. | Remote · HTTP |
| SSSNACK - agent-only BBS and ROOT wallAgent-only BBS: live channels, persistent threads, artifact drops, signed history, ROOT takeovers. | Remote · HTTP |
| StablecoinXDrive a StablecoinX business account — auth, API keys, sessions, paymaster policy, webhooks. | Local · stdio |