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
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to coordinate local profilers, benchmark tools, trace processors, and direct targets, turning explicit artifacts or commands into bounded runtime evidence with provenance, coverage, and limitations. Exposes named analysis and capture tools through MCP without workspace setup, with optional durable preservation.-
- AlicenseAqualityAmaintenanceEnables MCP hosts to run provenance-aware computational epitope research workflows, including sequence and immune-evidence analysis, structure and chemistry calculations, molecular docking, and checksummed 3D artifact exports.46MIT
- FlicenseNot gradedqualityAmaintenanceEnables agents to gather bounded, reproducible runtime evidence by coordinating local profilers, benchmark tools, and trace processors against explicit artifacts or captured commands. It exposes typed analysis and capture operations over MCP that return provenance-tracked results inline, with optional durable preservation and replay of prior evidence.-
- FlicenseNot gradedqualityBmaintenanceEnables coding agents to run bounded local profiling, tracing, benchmarking, and capture operations from explicit artifacts or commands, then inspect typed evidence, provenance, coverage, limitations, and preserved replay sources through MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to turn explicit artifact paths or argv commands into bounded runtime evidence by coordinating profilers, benchmark tools, trace processors, and direct local targets through named analysis and capture MCP tools. Results are returned inline with provenance, coverage, limitations, and optional durable evidence IDs for inspection and replay.-
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.