Skip to main content
Glama
marc-shade

Cluster Execution MCP Server

by marc-shade

Related Servers

Alternatives to Cluster Execution MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to orchestrate a heterogeneous machine fleet via SSH, with unified command execution, file transfer, and dispatch of coding agents across platforms.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives coding agents a single view of every machine you own, showing which GPUs and other resources are free across all of them, and lets the agent run commands there over SSH without credentials ever appearing in the chat.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing SSH-managed clusters with tools for executing commands, file operations, and tmux sessions across multiple nodes.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Transforms idle LAN machines into a unified compute cluster for AI agents to offload CPU-intensive tasks like simulations and backtesting. It provides a broker-worker architecture that integrates with MCP-compatible tools to distribute workloads across a local network.
      5
      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
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables LLMs to execute CLI commands and scripts for system deployment and management tasks, with support for directory listing, system info, and deployment templates.
      59 PyPI
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: cluster_bash for general command execution, cluster_status for monitoring, offload_to for explicit routing to a node, and parallel_execute for batch execution. There is no overlap in functionality.

    Naming Consistency2/5

    Tool names follow mixed conventions: cluster_bash and cluster_status share a prefix, but offload_to and parallel_execute use verb phrases without the prefix. The naming patterns are inconsistent, making it harder to infer the pattern at a glance.

    Tool Count4/5

    With 4 tools, the server is lean but covers the core functions of cluster execution. It could benefit from a dedicated node listing tool, but the count is appropriate for its scope.

    Completeness4/5

    The tool set covers the key operations: executing commands, getting status, explicit routing, and parallel execution. Minor gaps like the absence of a tool to list available nodes dynamically are present but do not severely hinder typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues