SSH Session MCP

Name: SSH Session MCP
Author: Zw-awa

by Zw-awaversion 2.7.1i★ –iRuns on your computer

Registry nameio.github.Zw-awa/ssh-session-mcp

Install

Overview

Description from the maker (original English)

Shared SSH PTY runtime for MCP clients with viewer, input lock, async tracking, and policy rules.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: SSH_PASSWORD

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: 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, SSH_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ssh-session": {
      "command": "npx",
      "args": [
        "-y",
        "ssh-session-mcp"
      ],
      "env": {
        "SSH_MCP_CONFIG": "your-value",
        "SSH_MCP_INSTANCE": "your-value",
        "VIEWER_PORT": "your-value",
        "VIEWER_HOST": "your-value",
        "AUTO_OPEN_TERMINAL": "your-value",
        "SSH_MCP_MODE": "your-value",
        "SSH_MCP_LOCAL": "your-value",
        "SSH_MCP_DEBUG": "your-value",
        "SSH_HOST": "your-value",
        "SSH_PORT": "your-value",
        "SSH_USER": "your-value",
        "SSH_PASSWORD": "your-value",
        "SSH_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add ssh-session --env SSH_MCP_CONFIG=your-value --env SSH_MCP_INSTANCE=your-value --env VIEWER_PORT=your-value --env VIEWER_HOST=your-value --env AUTO_OPEN_TERMINAL=your-value --env SSH_MCP_MODE=your-value --env SSH_MCP_LOCAL=your-value --env SSH_MCP_DEBUG=your-value --env SSH_HOST=your-value --env SSH_PORT=your-value --env SSH_USER=your-value --env SSH_PASSWORD=your-value --env SSH_KEY=your-value -- npx -y ssh-session-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ssh-session": {
      "command": "npx",
      "args": [
        "-y",
        "ssh-session-mcp"
      ],
      "env": {
        "SSH_MCP_CONFIG": "your-value",
        "SSH_MCP_INSTANCE": "your-value",
        "VIEWER_PORT": "your-value",
        "VIEWER_HOST": "your-value",
        "AUTO_OPEN_TERMINAL": "your-value",
        "SSH_MCP_MODE": "your-value",
        "SSH_MCP_LOCAL": "your-value",
        "SSH_MCP_DEBUG": "your-value",
        "SSH_HOST": "your-value",
        "SSH_PORT": "your-value",
        "SSH_USER": "your-value",
        "SSH_PASSWORD": "your-value",
        "SSH_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ssh-session": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ssh-session-mcp"
      ],
      "env": {
        "SSH_MCP_CONFIG": "your-value",
        "SSH_MCP_INSTANCE": "your-value",
        "VIEWER_PORT": "your-value",
        "VIEWER_HOST": "your-value",
        "AUTO_OPEN_TERMINAL": "your-value",
        "SSH_MCP_MODE": "your-value",
        "SSH_MCP_LOCAL": "your-value",
        "SSH_MCP_DEBUG": "your-value",
        "SSH_HOST": "your-value",
        "SSH_PORT": "your-value",
        "SSH_USER": "your-value",
        "SSH_PASSWORD": "your-value",
        "SSH_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SSH_MCP_CONFIG env
Optional explicit path to ssh-session-mcp.config.json when the config is not in the current working directory.
SSH_MCP_INSTANCE env
Optional runtime instance id used to isolate state across multiple MCP clients or agents.
VIEWER_PORT env
Viewer HTTP port. Use auto to allocate a free local port, or 0 to disable the browser viewer.
VIEWER_HOST env
Optional viewer bind host. Defaults to 127.0.0.1 for local-only browser access.
AUTO_OPEN_TERMINAL env
Set to true or 1 to automatically open the browser terminal when a session is created.
SSH_MCP_MODE env
Operation mode. safe blocks risky or unsuitable terminal actions by default, while full allows broader execution.
SSH_MCP_LOCAL env
Set to true or 1 to run a local shell instead of opening a real SSH connection. Useful for demos and offline testing.
SSH_MCP_DEBUG env
Set to true or 1 to expose browser-side debug controls intended for demos and local troubleshooting.
SSH_HOST env
Legacy single-target SSH host when not using ssh-session-mcp.config.json device profiles.
SSH_PORT env
Legacy single-target SSH port when not using ssh-session-mcp.config.json device profiles.
SSH_USER env
Legacy single-target SSH username when not using ssh-session-mcp.config.json device profiles.
SSH_PASSWORD secret env
Optional legacy password-based SSH authentication value.
SSH_KEY env
Optional path to a local SSH private key file for legacy single-target mode.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Zw-awa, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32678 servers in this category
Published to the registry more recently than 9% of the other 32678 servers in this category
Basic checks equal to or better than 100% of the other 32678 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is SSH Session MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SSH_PASSWORD

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.7.1) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Starreel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Starreel

by starreel

Turn a script into a finished, downloadable short-drama episode — via MCP or REST.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ssh-session-mcp

中文 | English

Persistent shared-terminal runtime for MCP clients over SSH.

ssh-session-mcp gives the user and the AI the same SSH PTY session, adds a browser viewer, tracks who typed what, and makes long-running remote work manageable instead of stateless.

Install At A Glance
Project Structure
Quick Start
Docker Status
MCP Tools
Configuration Summary
Security
Docs
Development

Install At A Glance

Normal users do not need to git clone this repository.
Preferred install path for MCP clients: npx -y ssh-session-mcp --viewerPort=auto
Preferred install path for human operators who want local binaries: npm install -g ssh-session-mcp
Official container distribution can be published to a public registry such as docker.io/zwawa/ssh-session-mcp
git clone is only for contributors, source builds, and local development.
For the common desktop MCP workflow, npx or a global npm install is still the lowest-friction path. Docker is mainly useful when you want a pinned runtime, container-based deployment, or registry-backed distribution.

Why It Exists

Most SSH-oriented MCP servers can execute commands, but they do not manage terminal state well enough for real collaboration.

ssh-session-mcp focuses on the missing runtime layer:

One shared PTY for both the human and the AI
Browser terminal for live inspection and manual intervention
Input lock so the AI does not type over the user
Safe/full execution modes for risky commands
Configurable default policy rules plus session-level custom rule overrides
Async command tracking for long-running remote work
Multi-device and multi-connection profile support
Local debug mode for demos, offline testing, and prompt iteration

Best Fit

AI-assisted remote development on Linux boards and SSH servers
Embedded, ROS, training, and deployment hosts that need a real terminal
Users who want the AI to help, but do not want to surrender the terminal
MCP Marketplace listings where the install and demo path must be clear

Project Structure

Key directories and files:

Path	Purpose
`src/`	Core TypeScript implementation for the MCP server, SSH session runtime, viewer, tools, and config CLIs
`src/viewer-html/`	HTML page generators and browser-side scripts for the terminal viewer
`test/`	Vitest coverage for runtime behavior, viewer contracts, config loading, and repository validation
`docs/`	Supporting documentation such as contracts, failure taxonomy, platform notes, and Docker usage
`docs/examples/`	Example config files for normal and Docker-oriented setups
`scripts/`	Build, version sync, and local operator helper scripts
`deploy/helm/`	Helm chart for Kubernetes deployment in single-node or distributed v0 mode
`site/`	GitHub Pages landing page source
`dist/`	Generated static site output from `npm run build:site`
`build/`	Generated JavaScript output from `npm run build`
`Dockerfile`	Container image build definition
`docker-compose.yml`	Profile-based Docker Compose example
`docker-compose.env.yml`	Legacy `.env`-style Docker Compose example
`server.json`	MCP server metadata for marketplace-style distribution
`AGENT.md`	Primary agent/operator playbook
`llms-install.md`	Agent-focused installation and environment checklist
`.env.example`	Legacy single-target environment variable template

Quick Start

1. Agent-First Install (Auto-download on first run)

If the goal is to let Claude Code, Codex, or OpenCode install the server automatically, prefer npx -y ssh-session-mcp in the MCP command instead of a prior global install.

For Cline Marketplace and other agent installers, see llms-install.md. This repo is structured to be one-click installable through an npx -y ssh-session-mcp --viewerPort=auto command.

Claude Code

claude mcp add --transport stdio ssh-session-mcp -- npx -y ssh-session-mcp --viewerPort=auto

Windows note from the Claude Code docs: native Windows users should wrap npx with cmd /c for stdio MCP servers.

claude mcp add --transport stdio ssh-session-mcp -- cmd /c npx -y ssh-session-mcp --viewerPort=auto

Codex

codex mcp add ssh-session-mcp -- npx -y ssh-session-mcp --viewerPort=auto

OpenCode

OpenCode's opencode mcp add flow is interactive. Choose a local MCP server and use this command:

npx -y ssh-session-mcp --viewerPort=auto

If you prefer config instead of the interactive flow:

"$schema": "https://opencode.ai/config.json", "mcp": { "ssh-session-mcp": { "type": "local", "command": ["npx", "-y", "ssh-session-mcp", "--viewerPort=auto"] } } }

This is the closest thing to "automatic installation" for stdio MCP servers today: the MCP client stores the command, and npx -y downloads the package automatically the first time it runs.

2. Fastest Local Demo

npm install -g ssh-session-mcp

ssh-session-mcp-ctl launch --local --viewerPort=auto

This starts a local shell instead of SSH and opens the browser terminal, which is the easiest way to test the MCP runtime before touching a real server.

3. Register As An MCP Server

Use the MCP server binary directly when wiring a client:

# Global install

npm install -g ssh-session-mcp

Server command used by MCP clients

ssh-session-mcp --viewerPort=auto

# Claude Code

claude mcp add --transport stdio ssh-session-mcp -- ssh-session-mcp --viewerPort=auto

Codex CLI

codex mcp add ssh-session-mcp -- ssh-session-mcp --viewerPort=auto

If you prefer npx instead of a global install:

npx -y ssh-session-mcp --viewerPort=auto

4. Connect To A Real SSH Target

Create .env from .env.example:

cp .env.example .env

SSH_HOST=YOUR_DEVICE_HOST

SSH_PORT=22 SSH_USER=YOUR_DEVICE_USER SSH_PASSWORD= SSH_KEY= VIEWER_PORT=auto AUTO_OPEN_TERMINAL=false SSH_MCP_MODE=safe

Then launch:

ssh-session-mcp-ctl launch --viewerPort=auto

5. Multi-Device Config

For multiple boards or named targets, create ssh-session-mcp.config.json:

"defaultDevice": "DEVICE_A_ID", "devices": [ { "id": "DEVICE_A_ID", "host": "DEVICE_A_HOST", "port": 22, "user": "DEVICE_A_USER", "auth": { "passwordEnv": "DEVICE_A_PASSWORD" }, "defaults": { "term": "xterm-256color", "cols": 120, "rows": 40, "autoOpenViewer": true, "viewerMode": "browser" } } ] }

Discovery order:

--config=/path/to/config.json
Workspace ssh-session-mcp.config.json
User-global config
Legacy .env fallback

Important:

Config discovery is based on the MCP process working directory.
auth.password is intentionally unsupported. Use auth.passwordEnv or auth.keyPath.
Secrets belong in .env or the parent environment, not in repo-tracked JSON.

6. Docker Status

Public Docker images should be distributed through Docker Hub, with GitHub Container Registry as an optional secondary registry:

docker.io/zwawa/ssh-session-mcp:<version>

docker.io/zwawa/ssh-session-mcp:latest ghcr.io/zw-awa/ssh-session-mcp:

Recommended container launch for a real SSH target:

docker run --rm -i \

-p 8793:8793 \ -e VIEWER_PORT=8793 \ -e VIEWER_HOST=0.0.0.0 \ -e SSH_HOST=YOUR_DEVICE_HOST \ -e SSH_PORT=22 \ -e SSH_USER=YOUR_DEVICE_USER \ -e SSH_PASSWORD \ docker.io/zwawa/ssh-session-mcp:latest

Export the password in your shell first instead of placing it directly on the command line.

Recommended launch for profile-based config:

docker run --rm -i \

-p 8793:8793 \ -e VIEWER_PORT=8793 \ -e VIEWER_HOST=0.0.0.0 \ -e SSH_MCP_CONFIG=/workspace/ssh-session-mcp.config.json \ -v "$PWD/ssh-session-mcp.config.json:/workspace/ssh-session-mcp.config.json:ro" \ -v "/path/to/host/keys:/workspace/keys:ro" \ docker.io/zwawa/ssh-session-mcp:latest

Equivalent Compose example:

docker compose up -d

See docker-compose.yml for a ready-to-run example that mounts ssh-session-mcp.config.json, publishes the viewer on 8793, and uses SSH_KEY_DIR when set or falls back to a dedicated ./keys directory. For the full Docker guide, including the legacy .env compose variant and MCP client config snippets, see docs/docker.md. For a container-oriented profile example, see docs/examples/ssh-session-mcp.config.docker.example.json.

Container-specific notes:

The image defaults VIEWER_PORT to 8793 when unset so the browser viewer can be published reliably.
The image defaults VIEWER_HOST to 0.0.0.0 inside the container so the mapped port is reachable from the host.
AUTO_OPEN_TERMINAL defaults to false in the container because browser auto-open from inside a container is usually not useful.
Mount config files or SSH keys read-only when possible.
Prefer mounting SSH keys from a directory outside the repo root.
In docker-compose.yml, SSH_KEY_DIR overrides the default key mount path. If it is unset, Compose falls back to ./keys, not the repo root.
Avoid putting passwords directly on the command line. Prefer exported env vars, Compose .env, or --env-file.
For stdio MCP clients, Docker is viable, but host-native npx is still simpler unless your client explicitly prefers containerized commands.

Docker-based MCP client command examples:

# Claude Code

claude mcp add --transport stdio ssh-session-mcp -- docker run --rm -i -p 8793:8793 -e VIEWER_PORT=8793 -e VIEWER_HOST=0.0.0.0 docker.io/zwawa/ssh-session-mcp:latest

Codex CLI

codex mcp add ssh-session-mcp -- docker run --rm -i -p 8793:8793 -e VIEWER_PORT=8793 -e VIEWER_HOST=0.0.0.0 docker.io/zwawa/ssh-session-mcp:latest

For JSON-based MCP clients, the same pattern works by using docker as the command and passing the remaining run ... docker.io/zwawa/ssh-session-mcp:latest tokens as args.

This is useful when:

The primary workflow is a local stdio MCP server command, not a long-lived network service.
You want a pinned Node/runtime environment without a local install.
You need registry-based distribution for a team or managed host.
You want container-level isolation for the MCP server process.

For many users, publishing to npm and recommending npx -y ssh-session-mcp --viewerPort=auto is still the lower-friction install path.

Viewer And Collaboration Model

The browser viewer is not decorative. It is part of the workflow:

The user can see exactly what the AI did.
The AI can pause when the user takes over.
Password prompts, pagers, and editors become visible state instead of hidden failure modes.
Session diagnostics and history turn terminal debugging into something inspectable.

Marketplace-Friendly Flow

For users:

install -> launch viewer -> connect once -> keep the session alive -> let the AI help

For agents:

ssh-qu

Only the beginning is shown; read the rest in the repo

SSH Session MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Starreel

README from the maker

ssh-session-mcp

Contents

Install At A Glance

Why It Exists

Best Fit

Project Structure

Quick Start

1. Agent-First Install (Auto-download on first run)

Claude Code

Codex

OpenCode

2. Fastest Local Demo

3. Register As An MCP Server

Server command used by MCP clients

Codex CLI

4. Connect To A Real SSH Target

5. Multi-Device Config

6. Docker Status

Codex CLI

Viewer And Collaboration Model

Marketplace-Friendly Flow