PSR Cloud MCP Server
MCP server that exposes PSR Cloud HPC operations as AI tools, built on top of
pycloud (psr-cloud on PyPI).
Prerequisites
- Python 3.10+
- Credentials. The server picks one of two paths automatically — you only
need to set up the one that fits you:
- Personal Access Token (recommended). Go to
sso.psr-inc.com/profile, log in with your corporate PSR Google account, generate a token under PSR Cloud — Personal Access Tokens, and save it (shown only once). Then exportPSR_CLOUD_EMAILandPSR_CLOUD_ACCESS_TOKEN(see below). - PSR Cloud Desktop fallback. If you already have PSR Cloud Desktop
installed and signed in, leave both env vars unset — the MCP server will
reuse the credentials cached at
%APPDATA%\PSR\PSRCloud\EPSRConfig.xml. This path only works on Windows.
- Personal Access Token (recommended). Go to
Installation
From PyPI
pip install psr-cloud-mcp
From the Git repository
pip install git+https://github.com/your-org/psr-cloud-mcp.git
Local development clone
git clone https://github.com/your-org/psr-cloud-mcp.git
cd psr-cloud-mcp/local
pip install -e .
Configuring Claude Code
Add to ~/.claude/settings.json (or settings.local.json for local-only):
{
"mcpServers": {
"psr-cloud": {
"command": "psr-cloud-mcp",
"env": {
"PSR_CLOUD_EMAIL": "yourname@psr-inc.com",
"PSR_CLOUD_ACCESS_TOKEN": "<your-token>"
}
}
}
}
If you prefer not to store the token in the config file, omit the env block and
set the variables in your shell profile instead. Or, if you already have PSR
Cloud Desktop signed in, omit the env block entirely — the server will fall
back to the credentials saved by Desktop.
Configuring Claude Desktop
Open the Claude Desktop config file:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Add the psr-cloud entry under mcpServers:
{
"mcpServers": {
"psr-cloud": {
"command": "psr-cloud-mcp",
"env": {
"PSR_CLOUD_EMAIL": "yourname@psr-inc.com",
"PSR_CLOUD_ACCESS_TOKEN": "<your-token>"
}
}
}
}
If psr-cloud-mcp is not on the system PATH (common on Windows), use the full
path to the executable:
{
"mcpServers": {
"psr-cloud": {
"command": "C:\\Users\\<user>\\AppData\\Local\\Programs\\Python\\Python3xx\\Scripts\\psr-cloud-mcp.exe",
"env": {
"PSR_CLOUD_EMAIL": "yourname@psr-inc.com",
"PSR_CLOUD_ACCESS_TOKEN": "<your-token>"
}
}
}
}
To find the exact executable path on Windows, run:
where.exe psr-cloud-mcp
After saving the file, restart Claude Desktop. The PSR Cloud tools will appear in the tools panel (hammer icon).
Available tools
| Tool | Description |
|---|---|
list_cases |
List cases from the last N days |
get_cases |
Get details for specific case IDs |
get_case_status |
Poll execution status of a case |
get_case_log |
Retrieve execution log text |
list_download_files |
List result files available for a case |
run_case |
Submit a new model run |
cancel_case |
Cancel a running or queued case |
download_case_files |
Schedule a background download to a local path; returns a job_id |
get_download_status |
Poll a background download by job_id |
list_downloads |
List all background downloads tracked by this server |
list_clusters |
List the PSR Cloud clusters available to your account |
get_programs |
List available programs (SDDP, OPTGEN, …) |
get_program_versions |
List versions for a program |
get_execution_types |
List execution types for a program + version |
get_memory_per_process_ratios |
List valid memory ratio strings |
Choosing a cluster
Every cluster-scoped tool above accepts an optional cluster argument. Omit it
to use your account's default cluster — the right choice for most users. Pass a
name (run list_clusters to see them) to operate against a specific cluster;
unknown names are rejected with the list of valid options.
Typical AI workflow
get_programs()
→ get_program_versions("SDDP")
→ get_execution_types("SDDP", "18.0")
→ run_case(name="my-run", data_path="/path/to/data", program="SDDP", ...)
→ get_case_status(case_id) # poll until SUCCESS
→ list_case_files(case_id)
→ download_case_files(case_id, output_path="/path/to/results") # returns job_id
→ get_download_status(job_id) # poll until status is "done"
Metadata
Release files for psr-cloud-mcp 0.5.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| psr_cloud_mcp-0.5.4.tar.gz | 10.6 kB | With provenance | Details for psr_cloud_mcp-0.5.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| psr_cloud_mcp-0.5.4-py3-none-any.whl | Python 3 | none | any | Details for psr_cloud_mcp-0.5.4-py3-none-any.whl |
Total release size: 20.3 kB
Release files / psr_cloud_mcp-0.5.4.tar.gz
| Download URL | psr_cloud_mcp-0.5.4.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a9a816cf06912ae7381f9a5c3c8122c702261dfbcdff92b26b8d4516a4b24fe
|
|
BLAKE2b-256 checksum How to use checksums |
e333310131fed97491feb83fdb6ffe21661f30ece6892269f91410b5ba7189ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / psr_cloud_mcp-0.5.4-py3-none-any.whl
| Download URL | psr_cloud_mcp-0.5.4-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a2751612310c75bb41b8845ee96d72f780b6b802ca6e103a8d62f61ec73d8e8
|
|
BLAKE2b-256 checksum How to use checksums |
ce3a3b7b68ad008894ccf8aa8fbe79ecbb77f6df93962a19e2706015eb61a129
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logSecurity for psr-cloud-mcp 0.5.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for psr_cloud_mcp-0.5.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.