ssh-licco
Related Servers
Alternatives to ssh-licco
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to SSH into Linux servers, run commands, deploy code, and manage servers via natural language, also doubles as a CLI for manual use.3MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to manage remote servers via SSH with agentless command execution, file operations, and service management.921 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to maintain persistent SSH terminal sessions and transfer files to/from remote servers. Allows stateful command execution, natural language server management, and seamless file operations through SSH connections.6 npm36MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage remote servers via SSH, including command execution, multi-host batch operations, SFTP file transfer, background job handling, DevOps diagnostics, port tunneling, and safety guardrails like high-risk command blocking and read-only mode.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to execute SSH commands and transfer files to and from remote servers, supporting remote server management and seamless session transfer to a VPS.-
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to securely operate servers over SSH, including remote command execution and file transfer with a built-in web admin console and Windows tray app.21 npm1ISC
TDQS
Scored across 9 tools
Most tools are clearly distinct (connect, disconnect, keygen, file_transfer, docker, host), but three tools overlap on running things remotely in the background: ssh_execute (background/screen/tmux execution), ssh_process (start detached background process), and ssh_session (persistent screen/tmux sessions). The descriptions help differentiate them, but the boundaries between 'run in background', 'detached process', and 'persistent session' remain fuzzy and invite misselection.
Every tool uses a consistent ssh_<noun> snake_case pattern (ssh_connect, ssh_execute, ssh_file_transfer, ssh_generate_key, etc.). The uniform prefix and naming style make the set highly predictable.
Nine tools is well-scoped for an SSH management server. Each covers a distinct concern (connection, execution, transfer, keys, hosts, docker, processes, sessions) without padding.
The surface covers the full SSH lifecycle: connect/disconnect, command execution, file transfer, key generation, host config, plus docker/process/session/tunnel management. Minor gaps like listing or deleting generated keys and dedicated port-forward config outside ssh_process are workarounds rather than blockers.