MCP server that wraps the Dagster GraphQL API — manage runs, assets, schedules, sensors, and backfills from any MCP client
cloudHPC is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Run FDS, OpenFOAM, CalculiX and other engineering simulations on cloudHPC from your AI assistant.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http cloudhpc-mcp https://mcp.cloudhpc.cloud/mcp
# 2 — ask your agent for something these tools do
# list_solvers, list_machine_options, solver_guide and 19 more
cloudHPC costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http cloudhpc-mcp https://mcp.cloudhpc.cloud/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the solvers/scripts available on cloudHPC, grouped by family.
No parameter schema on file.
List the vCPU counts and RAM/instance types that can be requested.
No parameter schema on file.
How to prepare a case for a solver on cloudHPC: required input files, what cloudHPC does automatically, parallelism, resources, log files.
No parameter schema on file.
Suggest vCPU and RAM type for a run, following cloudHPC scalability rules.
No parameter schema on file.
List files and folders in the user's cloudHPC storage.
No parameter schema on file.
List the result archives of a case folder (FDS.tar.gz, OPENFOAM-*.tar.gz, ...).
No parameter schema on file.
Get a temporary download link for a storage file (e.g. "myCase/FDS.tar.gz").
No parameter schema on file.
Get a signed URL to upload one file into a storage folder (remote clients).
No parameter schema on file.
Delete a file or folder from storage. Irreversible.
No parameter schema on file.
Launch a simulation on a case folder already in storage. Costs money:
No parameter schema on file.
List the user's simulations, most recent first.
No parameter schema on file.
Get status and details of a simulation.
No parameter schema on file.
Wait until a simulation is no longer pending/running, or until max_minutes.
No parameter schema on file.
Ask a running simulation to upload partial results to storage now.
No parameter schema on file.
Stop a running simulation.
No parameter schema on file.
Start a remote desktop machine (static instance) for post-processing, e.g. ParaView or Smokeview on the results of a storage folder.
No parameter schema on file.
Resume a stopped or interrupted simulation: launch it again on the same storage folder with the SAME solver, vCPU, RAM type and instance type, so the solver continues from its restart data (FDS .restart files, OpenFOAM latest time). Tested for FDS and OpenFOAM only. vCPU and RAM are never
No parameter schema on file.
Get the browser remote-desktop (VNC) link of a running simulation.
No parameter schema on file.
Show the API rate limits and how many API requests have been made.
No parameter schema on file.
Inspect a local case folder: detect the solver and the model size.
No parameter schema on file.
Compress a local case folder and upload it to cloudHPC storage.
No parameter schema on file.
Download result archives of a storage folder to a local directory.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install cloudHPC or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.6.4.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish cloudHPC can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.