hpc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_test_connectionB | Check configured SSH connectivity and Slurm command availability. |
| project_ensureC | Register a local project and ensure its remote project directory exists. |
| project_statusC | Return the registered project mapping. |
| project_syncC | Incrementally upload project changes while preserving conflicts. |
| project_list_remote_changesC | Plan synchronization and report remote changes without uploading. |
| remote_listC | List a directory within a registered remote project. |
| remote_statC | Return metadata for a project-relative remote path. |
| remote_readC | Read bounded UTF-8 text with a SHA-256 revision for optimistic editing. |
| remote_searchC | Search for literal text inside the remote project with bounded results. |
| remote_apply_patchC | Apply text edits only when the remote revision and match counts agree. |
| remote_uploadC | Upload a file between paths confined to the registered project roots. |
| remote_downloadC | Download a remote file into the registered local project. |
| remote_executeC | Execute structured program arguments under the remote project and command policy. |
| slurm_watch_jobD | Verify local handoff registration. Run hpc-agent watch in the original Codex terminal first. |
| slurm_previewB | Preview a remote batch script without submitting a job. |
| slurm_submitB | Submit a validated batch script idempotently; reuse the request UUID on retries. |
| slurm_get_jobC | Inspect one registered job using the queue and accounting records. |
| slurm_list_jobsC | Inspect locally registered jobs only. |
| slurm_read_logC | Read a bounded chunk of a registered job log; default to its tail. |
| slurm_list_artifactsC | List bounded artifacts within a registered job's project output directory. |
| server_listA | List configured SSH aliases and public endpoint information without connecting. |
| ssh_executeB | Run a config-allowlisted command in an allowed directory; submit jobs with slurm_submit. |
| ssh_uploadB | Upload one regular file between configured allowed roots, replacing the destination. |
| ssh_downloadB | Download one regular file between configured allowed roots, replacing the destination. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Several tool pairs overlap heavily: ssh_upload/remote_upload, ssh_download/remote_download, and ssh_execute/remote_execute all perform essentially the same file/command operations, differing only in scope wording (allowed roots vs project roots). Descriptions hint at differences but an agent could easily misselect between them.
Names follow a predictable prefix+verb_noun snake_case pattern (project_*, remote_*, slurm_*, server_*). The one inconsistency is that equivalent operations get different prefixes (ssh_upload vs remote_upload), which slightly muddies the scheme but is still readable.
24 tools is on the heavy side of the 16-25 borderline band. The HPC scope (SSH, project sync, file transfer, Slurm lifecycle) broadly justifies the count, but several overlapping transfer/execute tools arguably inflate it.
Strong lifecycle coverage: project registration/sync, remote file ops, patch application, and a full Slurm surface (preview, submit, get, list, watch, read_log, list_artifacts). The notable gap is job cancellation/deletion, which agents may need.