One terminal. All your servers.

Open-source terminal SSH manager for macOS and Linux that keeps ~/.ssh/config in sync with your cloud infra. Spin up a VM, it shows up. Destroy it, it dims. Across 16 cloud providers.

purple
$

I had a perfectly good SSH config. Clean, well-organized, no complaints. That part worked.

What didn't work was the six other things I needed to do every day. Every container check was ssh, docker ps, scroll, repeat. Every file transfer was remembering scp flags. Every new cloud VM meant opening a console, copying an IP, editing my config by hand. And running the same command across a dozen hosts? That was either a bash loop or a whole Ansible setup for a one-liner.

So I put all of it in one terminal.

🔍 Find anything with one keystroke. Press : for Jump, a universal fuzzy search bar across hosts, tunnels, containers, snippets and actions. Searches the SSH User, ProxyJump and Vault SSH role too, so typing your username finds every server you log in as. Field prefixes user:, proxy:, vault: and tag: scope to a single SSH directive. Recent picks persist across sessions. Like Linear's Cmd+K, but in your terminal.
☁️ Your ssh config tracks your infra. Spin up a VM on AWS, Azure, GCP, Hetzner, Proxmox VE, Tailscale or 10 other cloud providers and it shows up in your host list. Destroy it and the entry dims. No more hand-editing after every Terraform run.
🐳 See and control containers remotely. Docker and Podman over plain SSH. Start, stop, restart without installing anything on the remote.
🚇 Watch your SSH tunnels in real time. Dedicated Tunnels page with live throughput, channel events and the apps moving bytes. Local, Remote and Dynamic SOCKS, all in one sortable view. Tab from the Hosts page.
📂 Browse and copy files between machines. Dual-pane file explorer. Local filesystem on one side, remote on the other. Handles ProxyJump chains and tunnels.
Run one command on many hosts. Pick a snippet, select your targets, execute. Results stream in per host.
🔑 Passwords handled for you. Plugs into OS Keychain, 1Password, Bitwarden, pass, the HashiCorp Vault KV secrets engine or a custom script. Credentials are fetched at connect time.
📜 Short-lived SSH certificates. Integrates with the HashiCorp Vault SSH secrets engine. Configure a role per host or per provider, press V to bulk-sign. Cached under ~/.purple/certs with automatic renewal.
🤖 Let AI agents manage your servers. Built-in MCP server with one-click .mcpb install for Claude Desktop. Works with Claude Code, Cursor, Windsurf and any MCP-compatible agent. Read-only mode and a JSON Lines audit log are built in.
📬 What's new overlay. Sticky toast and overlay summarizing releases since you last opened. Press n to reopen.
Cloud providers

FAQ
PURPLE(1)General Commands ManualPURPLE(1)
Does purple modify my SSH config?
Only when you explicitly add, edit, delete or sync. All writes are atomic with automatic backups. Comments, indentation and unknown directives are preserved.
Does it need a daemon or background process?
No. Single binary. Run it, use it, close it.
Does it send my config anywhere?
No. Your config never leaves your machine. Provider sync calls cloud APIs to fetch server lists. The TUI checks GitHub for new releases on startup (cached 24 hours). That's it.
Can I manage Docker containers with purple?
Yes. Press C on any host to list all containers over SSH. Start, stop, restart. Auto-detects Docker or Podman. No agent, no web UI, no extra ports.
Can AI assistants use purple?
Yes. Run curl -fsSL getpurple.sh | sh, then purple mcp to start the MCP server. Claude Code, Cursor, Windsurf and other agents get five tools: list_hosts, get_host, run_command, list_containers and container_action. Pass --read-only to restrict it to list_hosts, get_host and list_containers. Every call is logged to ~/.purple/mcp-audit.log by default (JSON Lines, mode 0o600, run_command body redacted). Claude Desktop users can install the .mcpb bundle from GitHub releases for a one-click setup. Full setup guide on the wiki.
How do I troubleshoot connection problems?
Run with --verbose to enable debug logging, then purple logs --tail in another terminal. Logs are written to ~/.purple/purple.log with fault domain prefixes: [external] for remote/tool errors, [config] for local config issues. Set PURPLE_LOG=trace for maximum detail.
purple v3.8.02026-05-08PURPLE(1)
$ curl -fsSL getpurple.sh | sh