Skip to main content
Glama

Related Servers

Alternatives to remote-ssh-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables LLMs and automation agents to securely connect to and operate Linux/Unix hosts over standard OpenSSH, including command execution, interactive PTY sessions, SFTP file management, and dynamic multi-host connection handling. It also includes safety rules that block dangerous commands and truncates large outputs to protect model context.
      30
      0
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to safely access and administer remote machines over SSH using existing OpenSSH config, with typed tools for running commands, reading and writing files, listing directories, and retrieving file metadata.
      9
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to securely execute shell commands on remote SSH servers with granular per-host permission controls. Automatically discovers hosts from ~/.ssh/config and exposes dedicated tools for each allowed host to ensure proper authorization before remote execution.
      1,420 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.
      12
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    TDQS

    B3.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each dedicated tool has a clearly bounded purpose (docker_ps vs docker_logs vs docker_exec, sys_snapshot vs service_status vs http_probe), and exec explicitly instructs the agent to prefer a specialized tool. Minor overlaps remain: exec can do anything its peers do, docker_exec mirrors exec semantics on a container, and backup_file duplicates the automatic backup that file_write already performs on overwrite.

    Naming Consistency4/5

    The dominant pattern is domain_action (file_read, file_write, docker_ps, docker_exec, docker_logs, http_probe, xui_api), which reads predictably and groups related tools by prefix. Deviations are small but real: exec is a bare verb, and backup_file inverts the order (verb_resource) relative to the rest.

    Tool Count5/5

    Eleven tools is squarely in the well-scoped band for a remote-ops server, and each one maps to a recurring day-to-day task rather than a redundant variation. The broad exec escape hatch keeps the specialized set from needing to grow further.

    Completeness4/5

    Read/write/backup for files, container inspection and exec, system and service diagnostics, egress probing, and panel API access cover the core remote-ops lifecycle with no dead ends. Gaps are minor: no directory listing, file copy/move, or container lifecycle controls (restart/stop), all of which must fall back to exec.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues