hpc-mcp
Related Servers
Alternatives to hpc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA Windows-first MCP server that maintains persistent stateful SSH sessions to Linux servers, enabling Codex to run commands, manage files, and use sudo without exposing credentials.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients on Linux to drive the official Codex Computer Use and Browser Use runtime on a remote Windows PC over SSH, operating in the logged-in Windows desktop session.1MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.93 npmMIT
- AlicenseAqualityBmaintenanceBridges MCP clients such as Claude Code and Cursor to independent Codex app-server sessions, letting them start, poll, steer, review, compact, cancel, and answer prompts for asynchronous Codex tasks over local stdio or a remote authenticated WebSocket. Runs read-only by default, with workspace-write sandboxing only when a user explicitly enables it, and reports job status, model listing, and progress back to the client.101MIT
- AlicenseNot gradedqualityBmaintenanceLets web ChatGPT and other MCP clients explore, read, and edit files under allowed local project roots, run whitelisted commands such as git and npm, and hand off or resume coding tasks with the local Codex CLI, optionally over an OpenAI Secure MCP Tunnel.MIT
- FlicenseNot gradedqualityAmaintenanceExposes an authenticated local runtime over OpenAI Tunnel so ChatGPT can inspect authorized Windows workspaces, read bounded Git status and diffs, submit and cancel Codex CLI tasks, and use workspace Skills. It also brokers connections to optional loopback stdio or HTTP MCP services, such as Stata and Zotero, with explicit tool allowlists and loopback-only access.2-
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.