SSH Server Manager
A local-first SSH host and credential manager for humans and AI agents.
One CLI (serverctl) and a loopback-only web UI to add, import, test, and
connect to your servers — with every password and passphrase stored in your
operating system's native credential vault, never in a plaintext file.
简体中文说明 · Documentation · Security model · Website
🤖 Using an AI agent? The skill deploys to every agent on your machine in one line — dependencies, links, and health check included. See the agent deployment guide.
Why this exists
Most SSH managers make you choose between convenience and custody:
- Cloud-synced clients (subscription GUIs) keep your credentials on someone else's infrastructure.
- Plain
~/.ssh/configkeeps you in control but handles no passwords, no vault, and gives AI coding agents an easy way to leak secrets. sshpass-style wrappers put passwords in files, env vars, or shell history.
SSH Server Manager is different by construction:
| Property | How |
|---|---|
| Secrets never touch disk in plaintext | macOS Keychain / Windows Credential Locker / Linux Secret Service via keyring; unsafe backends are rejected as a hard error |
Your ~/.ssh/config is never modified |
A separate managed config is rendered and included alongside it |
| The web UI is unreachable from the network | Loopback-only bind, one-time launch token, CSRF + Origin checks, strict CSP |
| Revealing a stored secret requires re-auth | WebAuthn passkey (Touch ID / Windows Hello) or an Argon2id master password; grants are single-use and expire in 30 s |
| AI agents can drive it without seeing secrets | Every command has --json; SSH authentication happens through AskPass so secrets never appear in argv, env, logs, or model context |
| Host keys are always verified | StrictHostKeyChecking is never weakened, by policy and by code |
Quick start
git clone https://github.com/xiayh0107/servers-connect.git
cd servers-connect/ssh-server-manager
./scripts/bootstrap # Windows: scripts\bootstrap.cmd
./scripts/serverctl doctor # verify ssh, vault backend, and dependencies
Add a server and connect:
./scripts/serverctl credential add-password work-password # prompts locally, stores in OS vault
./scripts/serverctl server add web1 --hostname web1.example.com --username deploy --credential work-password
./scripts/serverctl server test web1
./scripts/serverctl connect web1
Or import everything you already have:
./scripts/serverctl server import # preview only
./scripts/serverctl server import --apply
Prefer a GUI? ./scripts/serverctl ui opens the local web interface in your
browser with a one-time tokenized URL.
Features
- Connection profiles — alias, host, port, user, project/scenario tags, notes, ordered ProxyJump chains (with cycle detection).
- Three credential kinds — vault-backed passwords, private keys with optional vault-backed passphrases, and ssh-agent/OpenSSH defaults. Credentials are reusable across servers and protected against deletion while referenced.
- OpenSSH import — parses your
~/.ssh/config(followingInclude), resolves each literal alias withssh -G, previews before applying. - Managed config rendering — atomic, user-only-permission writes to
~/.ssh/ssh-server-manager.conf; your original config always loads last so unrelated defaults keep working. - Connection testing —
server testreports latency and a classified error code (authentication-failed,host-key-untrusted,timeout,dns-failed, …) and records history. - Remote execution —
serverctl exec alias -- cmd args, with--shellfor pipelines,--stdin/--stdin-binaryfor streaming files,--reuse Nfor ControlMaster connection sharing (macOS/Linux), and--jsonfor machine-readable results. - Local web UI — manage servers and credentials, test connections,
create/rename/delete tags and bulk-assign searchable hosts, choose
system/light/dark themes, import config, browse remote directories read-only
over SFTP, copy file references for an agent, and reveal a stored secret
after passkey or master-password re-authentication. Connection status expires
instead of staying green. Inspect or shut down a background instance with
serverctl ui --status/--stop— no pid bookkeeping. - Diagnostics —
serverctl doctorchecks ssh availability and version, SFTP availability, vault backend safety, database and config paths, and Python dependencies.
Platform support
| macOS | Linux | Windows | |
|---|---|---|---|
| CLI + web UI | ✅ | ✅ | ✅ |
| Credential vault | Keychain | Secret Service (gnome-keyring / KWallet / KeePassXC) | Credential Locker |
| Secret reveal re-auth | Touch ID passkey or master password | passkey or master password | Windows Hello passkey or master password |
Connection reuse (--reuse) |
✅ | ✅ | — (OpenSSH ControlMaster needs Unix sockets; a warning is printed) |
Details and headless-server notes: docs/platforms.md. CI runs the full test suite on all three platforms.
For AI agents
This project ships as an Agent Skill (SKILL.md) so Claude Code, Codex, and other agents can manage servers safely: agents get structured JSON output and connection error classification, while the AskPass architecture keeps secrets out of the model's context by design.
The skill also encodes conversation UX, not just commands: agents answer
inventory questions from a single --json call, hand interactive shells to
your terminal and proxy follow-up commands through exec (connect
refuses to run without a TTY instead of hanging), and clean up a background
UI with serverctl ui --stop.
Deploy the skill with one line:
curl -fsSL https://raw.githubusercontent.com/xiayh0107/servers-connect/main/install.sh | sh
It links the skill into every detected agent (~/.claude/skills,
~/.codex/skills, …), installs dependencies, and runs doctor. Windows
uses install.ps1. See docs/ai-agents.md.
Documentation
| Doc | Contents |
|---|---|
| docs/installation.md | Per-platform install, requirements, bootstrap |
| docs/quickstart.md | First 10 minutes, common workflows |
| docs/cli.md | Complete serverctl reference |
| docs/web-ui.md | Web UI walkthrough and its security gates |
| docs/security.md | Threat model and security invariants |
| docs/platforms.md | Platform-specific behavior, headless Linux |
| docs/ai-agents.md | Using with Claude Code / Codex / MCP |
| docs/faq.md | Troubleshooting and common questions |
License
Metadata
Release files for ssh-server-manager 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ssh_server_manager-0.5.0.tar.gz | 97.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ssh_server_manager-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 186.6 kB
Release files / ssh_server_manager-0.5.0.tar.gz
| Download URL | ssh_server_manager-0.5.0.tar.gz |
|---|---|
| Size | 97.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
68555cb9270c93c03a8841567d72b36c9c4662b75207695fd0718d464820f0b8
|
|
BLAKE2b-256 checksum How to use checksums |
a74d5afeaf3ec51070c9f3e6462d4004c591cc9a41b36f640f6d37a78c529e83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency logRelease files / ssh_server_manager-0.5.0-py3-none-any.whl
| Download URL | ssh_server_manager-0.5.0-py3-none-any.whl |
|---|---|
| Size | 89.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f8c19f1fd4c6bbd72090bbeca2d71d1822e91e2f4a128b60c973ee709ea7acaa
|
|
BLAKE2b-256 checksum How to use checksums |
f9949d52237b66cd03f3f2fc68fd2efa7ff8ec0db04496e0bd4d0010ff66fca3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 18, 2026.
Transparency log