A
licenseB
qualityA
maintenanceEnables natural-language preparation, submission, monitoring, and diagnosis of Slurm jobs on the ROMEO HPC cluster via SSH.
47
1
MIT
RISBridge MCP
by CodeMonk6
Related Servers
Alternatives to RISBridge MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables users to work on a SLURM HPC cluster over SSH through plain-language requests, covering file browsing and editing, batch job generation and submission, queue monitoring, and log reading to debug failed jobs. It runs with built-in safety guardrails such as fixed commands and configurable path policies for reads and writes.27MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Slurm HPC clusters via SSH, allowing job submission, monitoring, and error diagnosis through MCP clients like Claude Desktop.6MIT
- AlicenseNot gradedqualityAmaintenanceEnables managing OpenI platform resources (login, query nodes, submit jobs, view logs) via natural language in Claude or Codex, following a kubectl/docker-style CLI.138MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI-driven COMSOL batch jobs on the Harvard FASRC cluster, allowing users to run COMSOL models, manage jobs, and fetch results directly through natural language.23 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage SLURM cluster jobs with safety guardrails, including file transfer, job submission, log reading, and remote command execution.1MIT
TDQS
B3.2/5.0
Scored across 53 tools
Disambiguation3/5
The set has many well-described but overlapping tool clusters: ris_run wraps ris_submit_python_job; planning is split across ris_plan_run, ris_researcher_wizard, ris_estimate_resources, and ris_generate_sbatch_template; environment building appears in both ris_ensure_env and ris_submit_conda_env_job; job diagnostics overlap among ris_explain_job, ris_analyze_efficiency, and ris_compare_runs. Detailed descriptions help, but an agent must still disambiguate among similar submission, planning, and worker tools.
Naming Consistency4/5
All tools use a consistent ris_ prefix and lower_snake_case, with a strong verb_noun pattern for most names such as ris_submit_python_job, ris_cancel_job, and ris_list_my_jobs. A few deviate into noun phrases or bare verbs (ris_run, ris_job_history, ris_gpu_status), but the overall convention is predictable.
Tool Count1/5
53 tools is an extreme mismatch for a single MCP server, exceeding the 50+ anchor and the 25+ 'too many' threshold. Even for a broad HPC workflow, the surface is bloated with wrapper, variant, setup, and worker-specific tools that could be consolidated.
Completeness5/5
The server covers a remarkably complete HPC lifecycle: SSH/auth setup, profile discovery, partition/GPU inspection, project and file management, job planning, many job submission types, job control, logs, environment management, efficiency analysis, pipelines, and worker-based execution. No obvious core operation is missing for the stated RIS/Slurm domain.
Maintenance
ActivityInactive
ResponsivenessNo issues