Skip to main content
Glama

Related Servers

Alternatives to RunBeacon

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for monitoring and managing long-running processes on a remote VPS via SSH, with tools for status, logs, record summaries, and arbitrary command execution.
      6
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Durable MCP server for managing long-running jobs locally, over SSH, or on Slurm clusters. Jobs survive client disconnects and return exit codes, bounded logs, and JSON artifacts.
      11
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for infrastructure discovery and remote management, enabling SSH command execution, file transfer, log tailing, and machine/service inventory with a companion web dashboard.
      2
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that enables running structured commands and fleet operations on SSH hosts, supporting secure file transfer, persistent sessions, and bastion-based discovery.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for remote machine operations via SSH, providing a single tool to execute any shell command on remote machines with real-time progress streaming.
      58
      MIT

    TDQS

    A3.7/5.0

    Scored across 21 tools

    Disambiguation4/5

    Tools are mostly distinct, with clear separation between job operations, credential profiles, and specific password/token storage. The main potential confusion between job_wait and job_watch is resolved by descriptions clarifying one is for models and the other for dashboard long-polling.

    Naming Consistency4/5

    Tool names follow a consistent object_verb pattern (e.g., job_start, credential_profile_delete, audit_query). Verbs are consistently placed at the end, and no camelCase or mixed conventions are present. While some verbs like 'manage' are generic, the overall pattern is predictable.

    Tool Count3/5

    With 21 tools, the server spans multiple domains (jobs, credentials, GitHub publishing, policies, events, audit). This is on the heavier side but remains justified by the broad feature set; however, it borders on feeling cluttered for a single server.

    Completeness4/5

    The tool set provides solid lifecycle coverage for jobs (start, wait, cancel, list, snapshot, dashboard) and credential profiles (save, delete, list, set/clear default). Minor gaps exist, such as no explicit job retry mechanism and runner management limited to probing, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues