Skip to main content
Glama
romelllo

slurm-mcp

by romelllo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to slurm-mcp

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.
      7 npm
      4
      -

    • tacc-mcp-bio

      Narasimhan-Lab
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code to interact with a TACC or SLURM HPC cluster for bioinformatics pipelines, allowing job management, log reading, file browsing, remote script execution, and job submission through natural language.
      -

    • HPC MCP

      mfukudaQED
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to manage Linux HPC clusters from ChatGPT via an outbound Secure MCP Tunnel, with read-only and opt-in filesystem, command execution, background process, and Slurm/PBS scheduler tools.
      MIT
    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 27 tools

    Disambiguation4/5

    Tools are mostly distinct by resource and action, but a few overlap: read_file vs head/tail file, queue vs job_history, job_details vs job_efficiency, and generate_rmd vs generate_rmd_render_job. Descriptions clarify current vs past, full details vs efficiency, and template vs render job, so misselection risk is moderate rather than severe.

    Naming Consistency4/5

    All tools use the hpc_ prefix and snake_case, which is highly predictable. The main deviation is that many names are noun-first (hpc_queue, hpc_cluster_info, hpc_job_details) rather than strict verb_noun, but the convention remains consistent and readable.

    Tool Count3/5

    With 27 tools, the set is heavy, above the ideal 3-15 range and just over the 25+ 'too many' threshold. The broad HPC domain justifies many tools, but some file and job-query functions could likely be consolidated without losing capability.

    Completeness4/5

    The surface covers docs, filesystem browsing/reading, storage, project resolution, queue/partition info, job details/efficiency/history, reservations, submit/cancel/hold/release, and script generation. Minor gaps remain: no delete/move/copy for files, no job update or array-specific submission, and write/edit/submit depend on a writable location that the description says is not configured.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources