MCP Ssh Manager

Name: MCP Ssh Manager
Author: bvisible

by bvisibleversion 4.0.3i★ –iRuns on your computer

Registry nameio.github.bvisible/mcp-ssh-manager

Install

Overview

Description from the maker (original English)

SSH for AI agents: commands, files, backups and health, with approval, a vault and an audit trail

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: Clinics & health

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_CONFIG_PATH, SSH_ENV_PATH

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-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ],
      "env": {
        "SSH_CONFIG_PATH": "your-value",
        "SSH_ENV_PATH": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add ssh-manager --env SSH_CONFIG_PATH=your-value --env SSH_ENV_PATH=your-value -- npx -y mcp-ssh-manager

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-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ],
      "env": {
        "SSH_CONFIG_PATH": "your-value",
        "SSH_ENV_PATH": "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-manager": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-ssh-manager"
      ],
      "env": {
        "SSH_CONFIG_PATH": "your-value",
        "SSH_ENV_PATH": "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_CONFIG_PATH env
Path to a TOML file holding the server definitions. Defaults to ~/.codex/ssh-config.toml. Each server can set MODE to readonly or restricted to constrain what the agent may run.
SSH_ENV_PATH env
Path to a .env file declaring servers as SSH_SERVER_ _HOST, _USER, _KEYPATH and friends. Defaults to a .env next to the package.

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 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account bvisible, 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 Clinics & healthi

More stars than 0% of the other 862 servers in this category
Published to the registry more recently than 93% of the other 862 servers in this category
Basic checks equal to or better than 100% of the other 862 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 MCP Ssh Manager 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

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 (4.0.3) reached the registry yesterday.

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: Mirobody, FHIR MCP Server, Google Health MCP

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

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated 5 days ago

Install

FHIR MCP Server

by wso2

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 8 days ago

Install

Google Health MCP

by davidmosiah

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

Runs on your computer★ 79MITUpdated 4 months ago

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.

You give your agents a shell, and you see what they do with it.

An MCP server for SSH. Let Claude Code , Claude Desktop and OpenAI Codex (or any MCP client)

work on your real servers — run commands, move files, query databases, take backups, check health —

and watch over their shoulder while they do it.

Twenty seconds, unedited — watch full size . Real SSH, real SFTP, three throwaway hosts on the loopback.

The problem, in one line

An MCP SSH server is the most dangerous tool you can hand an agent: a shell on machines that matter. Today, when your agent runs something on production, you find out afterwards — if you find out at all.

This one lets you watch, and lets you say no. It is also, on the boring days, simply a very good way to let an assistant do the server work you were going to do yourself.

Choose your workspace

Desktop application (`4.0.3`): one installation with its own runtime, terminal, file browser and server settings. No separate Node.js or npm installation. Download it:

Platform	File	Signature
macOS, Apple silicon / Intel	`…-arm64.dmg` / `…-x64.dmg`	Signed and notarized by Apple — opens normally
Windows x64 / arm64	`…-setup.exe`	Not code-signed in 4.0.x. Windows shows "Windows protected your PC": More info → Run anyway. Check the file against the SHA-256 in `release-manifest-win32.json` on the release (`ssh-manager app` does it for you). Signing comes in a later release.
Linux x64	`.deb`, `.AppImage`	Unsigned, as Linux packages usually are

Already using npm / the CLI? npm update -g mcp-ssh-manager brings 4.0.3, and the V4 engine runs without an interface, from your existing .env, TOML or process variables — no automatic import, no forced wizard, no approval prompt unless you enable one per server. The one behaviour that tightens is SSH host-key verification; read that section of the upgrade and rollback guide before upgrading. To stay on 3.8 for now, pin it: npm install -g mcp-ssh-manager@3.

From the engine to the application in one step. With a V4 engine installed, ssh-manager app downloads the desktop application of the engine's own version, checks it against the release (size and SHA-256 from the release manifest, and on macOS Apple's signature and notarization), installs it and opens it — or just opens it when it is already there. The browser interface of ssh-manager control offers the same as one button. Your agents keep using the npm engine; the application is the window on top of it. Nothing is downloaded unless you ask.

Without npm at all. The application carries the engine too, and your AI tools can start that one: *Options → AI tools* lists Claude Code, Claude Desktop and Codex, says which ssh-manager each one starts (npm's, the application's, or none yet) and switches it in one click — no Node, no terminal. The same tab, in ssh-manager control, shows npm users which version each tool really runs. A switch rewrites that tool's one ssh-manager entry, keeps its environment variables, and takes effect when the tool next starts; switching back is the same click.

Updates. The application checks for a new version at launch and every six hours and says so where you will see it: a mark on the sidebar, *Options → Updates* (the running version, the one on offer, a *Check now* button, release notes) and, once per version, a notification. Downloading is a click, and installing is a second one (*Restart to update*) or happens when you quit. The npm engine updates with npm, on its own schedule. A change to the interface reaches npm users with the next npm release and application users with the next application release.

Up and running with npm

npm install -g mcp-ssh-manager     # or: brew tap bvisible/mcp-ssh-manager https://github.com/bvisible/mcp-ssh-manager && brew install ssh-manager

ssh-manager server add # guided: host, user, key or password claude mcp add ssh-manager mcp-ssh-manager

That's it. Restart Claude Code and ask it something.

Using Codex, a source checkout, or a project-scoped install?

OpenAI Codex — same install, then two files. In ~/.codex/config.toml:

[mcp_servers.ssh-manager]

command = "mcp-ssh-manager" env = { SSH_CONFIG_PATH = "/Users/you/.codex/ssh-config.toml" } startup_timeout_ms = 20000

And your servers in ~/.codex/ssh-config.toml:

[ssh_servers.production]

host = "prod.example.com" user = "admin" key_path = "~/.ssh/id_rsa" default_dir = "/var/www" group = "production"

Everything below works identically from Codex — same 37 tools, same config fields.

From source:

git clone https://github.com/bvisible/mcp-ssh-manager.git

cd mcp-ssh-manager && npm install cd cli && ./install.sh claude mcp add ssh-manager node /absolute/path/to/mcp-ssh-manager/src/index.js

The MCP engine needs no build. To use the interface (ssh-manager control) from a checkout, build it once: npm run build:ui (the published package and the desktop app already carry it).

Scopes — --scope project writes an .mcp.json your team can commit; --scope user enables it everywhere for you.

Prerequisites — Node 18+, on Linux, macOS or Windows. rsync for ssh_sync, sshpass only if you sync with password auth (brew install hudochenkov/sshpass/sshpass, or apt-get install sshpass).

Then just ask

No syntax to learn. Your assistant already knows how to use the 37 tools; you talk to it in your own words.

You say	What happens
"Why is production slow right now?"	CPU, memory, disk, load average and the top processes, in one round trip
"Back up the database before I deploy."	A compressed, timestamped MySQL/PostgreSQL/MongoDB dump with a retention policy
"Tail the nginx error log on staging."	Live output, streamed as it happens
"Push ./dist to production:/var/www and restart nginx."	The files out, then the restart — with ownership, permissions and a rollback copy handled
"Which of my servers is running out of disk?"	Every server in the group, checked in parallel
"Open a tunnel to the production database."	Local port forward, so your GUI client just connects
"Run `docker ps` on everything tagged production."	One command, the whole group, sequential or parallel

There is a CLI too, for when you'd rather do it yourself: ssh-manager with no arguments opens this.

Watch over its shoulder — the control plane

New in 4.0.0. The application is opt-in: with no vault and no approval enabled, the engine keeps working headlessly, exactly as 3.8.x. See the migration guide for host-key verification and recovery behaviour.

ssh-manager control          # prints a local URL — or `ssh-manager app` for the desktop app

One thing in two wrappers. ssh-manager control runs the whole interface in a browser tab with nothing extra to install; the desktop builds for macOS, Windows and Linux are that same page with the engine inside them, so they need neither Node nor the npm package.

The desktop build adds the two things a browser tab cannot do:

It lives in the menu bar. The icon carries a count when something is waiting, and its menu lists what is blocked on you, which shells and commands are open right now, and your servers — so "is anything waiting on me?" costs a glance instead of a window switch. Closing the window leaves it there rather than quitting.
It posts real system notifications, with the application's own identity, so macOS and Windows show and route them properly. Destructive requests stay on screen instead of fading after four seconds. macOS asks your permission the first time it needs to.

Stop it before it runs

The agent pauses and waits. You see the machine, the user, the tool, and the command in full — wrapped, never truncated, because half a command is how you approve the wrong thing. A desktop notification fires when something is waiting, because the request that goes unseen is the one that times out and is denied.

Approval is switched on from the interface, per server — not from a file:

Servers → the server → Approval → never (default) | destructive | always

Approval is stored in the vault and cannot be overridden by .env or process variables. Editing connection details preserves it. This prevents accidental configuration overrides from disabling the gate; it is not a security boundary against a process that already controls your local user account or vault files. If you had SSH_SERVER_*_APPROVAL set in a file, the engine says so on every start rather than quietly leaving you unprotected.

The destructive list is deliberately short. A prompt that cries wolf gets clicked through without being read, which is worse than no prompt at all: systemctl restart does not interrupt you, systemctl stop does.

When a request requires approval, a timeout, unreachable socket or disconnected control plane denies it. If nothing is listening, start ssh-manager control or the desktop app before retrying. Servers with approval disabled keep working headl

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

MCP Ssh Manager

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 Clinics & healthi

Common questions

Alternatives

Mirobody

FHIR MCP Server

Google Health MCP

README from the maker

The problem, in one line

Choose your workspace

Up and running with npm

Then just ask

Watch over its shoulder — the control plane

Stop it before it runs