M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionCLIO SlurmMCP server for Slurm workload management and HPC job schedulingHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS64 / 100 · C77 / 100 · B
Reliability10 / 2012 / 20
Security and permissions14 / 2016 / 20
Maintenance14 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Scientific computing users who need Slurm cluster management.
  • AI agent developers who want to automate HPC job lifecycles.
  • Hevy PRO users who want AI assistants to directly access their workout data
  • People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
  • Anyone needing summaries and insights from their training data
Not for
  • Systems that do not use Slurm as their scheduler (e.g., PBS, LSF).
  • Users who require a graphical interface or interactive terminal sessions.
  • Users who prefer manually scripted Slurm jobs over AI-driven interactions.
  • Users without a Hevy PRO subscription (API key required)
  • Users who want to use the server without an API key
  • Those needing delete workflows (Hevy API does not expose delete endpoints)
Required permissions
  • Requires access to Slurm commands (e.g., `sbatch`, `squeue`, `scontrol`, `scancel`, `sinfo`).
  • Depends on execution environment: listing jobs typically requires only user-level permissions; canceling or submitting jobs may require additional authorization.
  • May require access to the filesystem where job output files are stored.
  • Requires HEVY_API_KEY environment variable for Hevy API authentication
  • Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
  • Read operations can fetch workouts, routines, folders, templates, history, and user info
Risks and side effects
  • The `slurm_cancel` tool is destructive—it cancels jobs, potentially losing progress. The built-in `confirm_job_id` mechanism helps prevent accidental cancellation, but misuse can still have impact.
  • Resource submission can consume significant cluster resources, potentially affecting other users.
  • Sensitive information may be exposed through job descriptions or outputs.
  • Misconfiguration in a shared HPC environment could lead to permission issues.
  • API key can be misused if leaked; do not expose in URLs, logs, or screenshots
  • Create operations may produce duplicates on retry; update operations replace existing records
  • The server sends data to the Hevy API and may send telemetry to external services unless disabled
Supported clientsClaude DesktopClaude Desktop, Cursor, Codex, Antigravity
Tools526