Skip to main content
Glama
QiandingHuang666

clu

by QiandingHuang666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to clu

No user-submitted related servers found.

    Related Servers

    • mcp-slurm

      tejasvinu
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage SLURM HPC clusters via SSH. Supports job submission, resource monitoring, queue management, and file operations.
      8 npm
      4
      -

    • mcp-ssh

      DBeidachazi
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to establish and manage persistent SSH sessions, supporting smart command execution, async tasks, multi-host, sudo, and file operations through SFTP.
      15
      46 PyPI
      MIT

    • connect-to-server-mcp

      vstlmkh
      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

    • MCP SSH Session

      devnullvoid
      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

    • SSH MCP Server

      uarlouski
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely execute commands, transfer files, and manage port forwarding on remote servers via SSH.
      58 npm
      37
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (exec vs submit vs alloc, session_* vs jobs, upload vs download). Minor overlap exists between status and resources for cluster overview, and between log and session_info for log tail, but descriptions help differentiate.

    Naming Consistency3/5

    Naming mixes short imperative verbs (exec, submit, alloc, cancel, log) with prefixed noun patterns (ledger_query, session_list, connection_list). The set is readable but not a single consistent verb_noun convention.

    Tool Count5/5

    15 tools is well within the typical 3–15 range and each tool maps to a distinct capability (remote exec, job lifecycle, resource query, session management, file transfer, connection listing). No obvious redundant tools.

    Completeness4/5

    Core workflows are covered: command execution, job submission/monitoring/cancel, resource allocation, session management, and file transfer. Minor gaps include no dedicated job detail/history tool (e.g., sacct) and no connection create/delete management, though workarounds via exec exist.

    Resources