dtu-hpc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hpc_statusA | Check whether the DTU control plane is authenticated and connected. Call this first in any session. If it reports the daemon is unavailable, the user must start and authenticate it themselves -- you cannot do it for them. |
| hpc_operationsB | List every cluster operation the policy layer permits, with parameters. |
| hpc_whoamiA | Identity, groups, login node and home directory on the DTU cluster. |
| hpc_quotaB | Storage quotas for home and work3. |
| hpc_queuesA | List LSF queues, or show full limits for one queue. Args: queue: Optional queue name (e.g. "gpua100"). Omit to list all queues. |
| hpc_gpu_entitlementA | Report which GPU queues this account may submit to, and their caps. Use this before designing any GPU experiment: walltime ceilings and per-user slot limits determine whether a run must be split into a checkpointed chain. |
| hpc_gpu_nodesB | Current GPU node availability. |
| hpc_jobsB | All of this user's LSF jobs, including recently finished ones. |
| hpc_job_statusA | Full detail for one job. Args: job_id: Numeric LSF job id. |
| hpc_job_historyB | Scheduling history for one job -- why it pended, why it exited. Args: job_id: Numeric LSF job id. |
| hpc_sync_projectA | Upload the project's source files to its remote root on the cluster. Run this BEFORE submitting, whenever local code has changed — the connector does not upload anything automatically, and a job will happily run stale code. Source and configs only: files over 4MB are refused, and datasets or model weights must go via the transfer node or be downloaded by the job. Args: profile_path: Path to the local profile YAML (its sync_include / sync_exclude patterns decide what is sent). project_dir: Local project directory to upload from. dry_run: List what would be uploaded without sending anything. |
| hpc_fetch_logA | Read a log or small text file from inside the project jail (tail semantics). Args: path: Absolute remote path, must be under an allowed project root. max_bytes: How much of the end of the file to return (cap 512KB). |
| hpc_job_efficiencyA | CPU and memory efficiency of a job vs. what it requested. Check this after every substantial run and tighten the next request accordingly. Args: job_id: Numeric LSF job id. |
| hpc_gpu_modelsA | Live GPU models and availability in a queue. Use before A100 jobs: gpua100 mixes 40GB and 80GB nodes and there is NO selector to force 80GB. Args: queue: GPU queue name (e.g. "gpua100"). |
| hpc_pending_reasonA | Why a pending job is pending, in the scheduler's own words. Args: job_id: Numeric LSF job id. |
| hpc_render_jobA | Render the LSF job script a submission WOULD use, without submitting. Use this to show the human a script before the first run of a new profile. Args: profile_path: Path to the local profile YAML. run_id: Short identifier for this run (e.g. "exp03"). resource_overrides: Optional JSON object overriding profile resources, e.g. '{"walltime": "04:00", "gpus": 1}'. |
| hpc_submit_runA | Submit a single job from a profile. Caps are enforced; runs above the profile's confirmation thresholds require an explicit yes from the human. Args: profile_path: Path to the local profile YAML. run_id: Short identifier for this run. Also names the local manifest. project_dir: Local project directory (manifests land in runs//). resource_overrides: Optional JSON object overriding profile resources. confirmed_by_user: Set ONLY after the human explicitly approved an above-threshold run in conversation. |
| hpc_submit_chainA | Submit a checkpoint-resume chain of dependent jobs for runs longer than the 24h GPU walltime cap. The training command must support --resume-from and checkpoint on SIGUSR2 -- verify this BEFORE submitting. Args: profile_path: Path to the local profile YAML. run_id: Short identifier; segments become .0, .1, ... project_dir: Local project directory for manifests. segments: Number of walltime-sized segments (total = segments x walltime). resource_overrides: Optional JSON object overriding profile resources. confirmed_by_user: Set ONLY after explicit human approval when above the profile's confirmation thresholds. Chains are always above the 12h default threshold in total, so this usually requires asking. |
| hpc_cancelA | Cancel one LSF job. Only cancel jobs this project submitted. Args: job_id: Numeric LSF job id. |
| hpc_auditB | Recent control-plane actions, newest last. Args: limit: How many entries to return. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/PV-Bhat/dtu-hpc-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server