Ansys Research Runner MCP
Related Servers
Alternatives to Ansys Research Runner MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides MCP access to plan and execute reproducible computational experiments with immutable execution plans, artifact provenance, verification checks, and support for direct, Slurm, and PBS backends.17Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Codex to control Ansys Workbench and ICEM CFD locally, executing scripts, managing projects, and running simulations.2MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to control the local Open Science research application, including creating projects, starting or continuing research sessions, inspecting progress and plans, canceling runs, and reading generated artifacts.12Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents and MCP clients to run research as an explicit scientific process: forming hypotheses, designing and executing sealed experiments, capturing observations and artifacts, linking claims to supporting evidence, and reviewing provenance. Exposes coordinated MCP services so users can inspect, reproduce, and audit every step from question to conclusion rather than trusting an opaque final answer.462,530 PyPI2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables evidence-first CAE automation on Windows through local MCP servers for FreeCAD, Elmer FEM, and ParaView, supporting validated workflows from CAD to simulation and post-processing with a shared safety and evidence runtime.4MIT
- AlicenseNot gradedqualityFmaintenanceEnables reviewing grant application text, running deterministic eval cases, and executing Office of Research Aid packet workflows through MCP.Apache 2.0
TDQS
Scored across 10 tools
Each tool maps to a distinct stage of the research-run lifecycle: environment check, geometry inspection, region resolution, validation, planning, execution, status, cancellation, summary, and artifact listing. Even adjacent tools like validate_run and plan_run are separated by validation versus immutable CAE-IR compilation.
Tool names overwhelmingly follow a clear imperative snake_case verb_noun pattern (inspect_model, start_run, cancel_run, list_run_artifacts). The lone exception is doctor, a single-word diagnostic command that is conventional but breaks the pattern.
Ten tools is well-scoped for the pipeline: four pre-execution/setup tools, three run-control tools, and three result/artifact tools. No tool feels redundant or out of place.
The set covers the full lifecycle from environment/model inspection through recipe validation and planning, run execution/status/cancellation, and post-run summary/artifact discovery. It deliberately avoids field-array transfer and recipe editing, which are likely outside the runner's scope.