Skip to main content
Glama

Related Servers

Alternatives to mcp-hostops

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables remote file operations and command execution across multiple machines via SSH. Supports reading files, listing directories, and running commands on any host configured in your SSH config.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables executing commands and transferring files over SSH on multiple hosts concurrently, with auto-discovery from SSH config and support for various authentication methods.
      3
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to establish and manage persistent SSH connections to remote hosts for executing commands. Supports SSH config files, multi-host management, and automatic reconnection with thread-safe concurrent operations.
      15
      11
      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.
      7,828
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables executing commands on remote SSH hosts, with full support for bastion/jump hosts and ~/.ssh/config, plus Slurm job management and rsync.
      3
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote server management via SSH, including command execution, file transfer (SFTP), and interactive shell sessions, with support for multiple hosts.
      -

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation4/5

    The SSH tools are mostly well-separated by action and resource (e.g. run vs start, list_hosts vs check_hosts, remove_host vs forget_host), and descriptions clarify edge cases. The llms_* tools form a separate, also distinct suite, though a few pairs like run/start and list_hosts/check_hosts could momentarily confuse.

    Naming Consistency4/5

    All tool names use snake_case, with a consistent verb_noun pattern for resource actions (list_hosts, add_host, remove_host, llms_add_source) and imperative verbs for standalone actions (run, start, kill). Minor deviations like llms_index (noun) and the llms_ prefix split are readable but not perfectly uniform.

    Tool Count3/5

    19 tools is on the heavy side (rubric borderline 16–25) and the server bundles an SSH host-management suite with an unrelated llms.txt documentation suite, so the total feels inflated for the stated hostops purpose. Each tool earns its place within its subdomain, but the combined count is not tightly scoped.

    Completeness4/5

    Core host lifecycle (list, get, check, add, remove, trust, forget, copy_id) and command execution (run, start, get_job, list_jobs, kill) are covered, with no major dead ends. Minor gaps like an explicit host-update tool (add replaces managed blocks) and file transfer remain, and llms tools cover source management plus index/search/fetch.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues