mcp-ssh-manager weekly downloads statistics

<p align="center"> <img src="docs/images/icon.png" alt="" width="96"> </p> <p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="docs/images/wordmark-dark.png"> <img src="docs/images/wordmark.png" alt="SSH Manager" width="380"> </picture> </p> <h1 align="center">You give your agents a shell,<br>and you see what they do with it.</h1> <p align="center"> <b>An MCP server for SSH.</b> Let <b>Claude Code</b>, <b>Claude Desktop</b> and <b>OpenAI Codex</b> (or any MCP client)<br> work on your real servers — run commands, move files, query databases, take backups, check health —<br> and watch over their shoulder while they do it. </p> <div align="center">

</div> <p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="docs/images/control-plane-dark.gif"> <img src="docs/images/control-plane.gif" alt="An agent asks to run rm -rf on production; the request is refused; a live command streams its output; every server is probed for health" width="900"> </picture> </p> <p align="center"> _{Twenty seconds, unedited — <a href="docs/videos/control-plane.mp4">watch full size</a>. Real SSH, real SFTP, three throwaway hosts on the loopback.} </p>

---

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.2): 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.2, 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…