tcs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TCS_MCP_CONFIG | No | Path to the tcs-mcp.config.json configuration file. If not set, a default direct profile allowing only the startup directory is used. | |
| TCS_MCP_PROFILE | No | Name of the profile to use from the configuration file. Required when multiple profiles exist, but optional if a default profile is defined or if using the default configuration. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| system_statusA | Check the selected profile, connection, runtime, TCS commands, and configured path limits. |
| list_jobsC | List this account's current jobs or completed job history in structured form. |
| get_jobA | Get details and output paths for one current or historical job. |
| get_job_statsA | Get basic or node-level statistics for a completed job. |
| list_resourcesA | Read PJM resource-group availability and this account's scheduler limits. |
| list_modulesA | List or search Environment Modules available on the login node. |
| list_filesB | List one directory inside configured remote roots. |
| read_fileA | Read the beginning of a text file, or tail a requested number of lines, inside configured roots. |
| search_filesB | Search text with ripgrep under a configured remote root. |
| validate_jobA | Validate either an existing PJM script or a structured normal-batch job definition without submitting it. |
| render_jobB | Render and validate a structured normal-batch job definition without writing it. |
| submit_jobB | Preview a normal-batch pjsub operation and return a confirmation token. Does not submit until confirm_action. |
| cancel_jobA | Preview cancellation of a current owned job and return a confirmation token. |
| run_commandC | Preview a constrained build or pre/post-processing command. Heavy computation must be submitted as a job. |
| write_fileC | Preview writing or appending a UTF-8 text file inside configured remote roots. |
| manage_filesB | Preview mkdir, copy, move, or delete inside configured remote roots. |
| transfer_filesC | Preview an SSH-mode upload or download between configured local and remote roots. |
| confirm_actionA | Execute exactly one previously previewed action using its short-lived, single-use token. |
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 18 tools
Most tools have distinct purposes (jobs, files, resources, modules, etc.). However, validate_job and render_job both handle structured job definitions, creating minor ambiguity about which to use for validation only. submit_job also performs a preview, but its confirmation token makes its role clear.
The vast majority of tools follow a clear verb_noun pattern (list_jobs, get_job, submit_job, read_file, etc.). The only outlier is 'system_status', which uses noun_noun instead of a verb-based name, breaking the otherwise consistent convention.
With 18 tools, the set is slightly above the ideal 3-15 range, but the breadth of functionality (job management, file operations, system status, and the preview/confirm flow) justifies the count. It is not bloated to the point of being overwhelming.
The tool surface covers the core HPC workflow: job submission/validation/cancellation/statistics, file reading/writing/searching/transfer, resource and module queries, and system status. Minor gaps exist, such as no direct job output/error viewing (though read_file can access output paths) and no job modification (update/alter), but these are workable.