JumpServer 443-only MCP bridge for coding agents
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-jumpserver-gui-sucks","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-jumpserver-gui-sucks **CAUTION: Operate production machines with extreme care. This MCP assumes no responsibility for production incidents caused by unsafe or incompetent model behavior.** A JumpServer 443-only MCP bridge for coding agents such as Codex and Claude. The project exposes a CLI-first, MFA-compatible, audit-preserving path into JumpServer assets without depending on port 2222 or any GUI-driven workflow in normal use. ## Current Status The main CLI and MCP chain is working against a real JumpServer instance: - CLI-first login with terminal-entered MFA - persisted durable `access_key` auth for REST discovery - persisted authenticated web-session cookies for KoKo terminal flows - asset, node, connect-method, and asset-access discovery - KoKo 443 WebSocket probing - one-shot remote command execution through KoKo - managed multi-turn terminal sessions for MCP-driven shell interaction - managed shell reuse for repeated command execution against the same asset/account target - non-blocking buffered terminal output reads for managed sessions - explicit managed-session command interruption with `Ctrl-C` - verified effective-user tracking and managed `sudo`/`su` login-shell transitions - process-local terminal idle reaping and session-cap enforcement - explicit cookie-session refresh probing before terminal work - a line-oriented CLI shell for non-MCP interactive terminal use - managed KoKo elFinder SFTP sessions over port 443 - remote directory listing, metadata, directory creation, upload, download, rename, and deletion - explicit overwrite and recursive-delete safety gates for file operations The current implementation is usable, but it is not feature-complete yet. The most important known limitation is: - terminal access still depends on a valid cookie-backed web session, so a fully expired terminal session still requires a fresh `login` run with MFA Terminal-oriented entry points now accept either the concrete JumpServer account ID/alias requir…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.