Ansys Research Runner MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANSYS_RESEARCH_ANSYS_ROOT | No | Path to a nonstandard Ansys installation root to use for the current process. Standard installations are discovered automatically. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| doctorC | Report installed host and PyAnsys capabilities. |
| inspect_modelC | Inspect one confined supported CAD model into a Geometry Graph. |
| resolve_regionsC | Resolve semantic regions referenced by one Run Recipe. |
| validate_runB | Validate one Run Recipe and all referenced contracts. |
| plan_runC | Compile a supported recipe into immutable reviewed CAE-IR. |
| start_runA | Enqueue a run and immediately return its durable QUEUED snapshot. |
| get_run_statusC | Return a job snapshot and its append-only event history. |
| cancel_runC | Request safe cancellation through the Job Registry. |
| get_run_summaryC | Return bounded scalar results without any field arrays. |
| list_run_artifactsB | List artifact paths, hashes, media types, and sizes only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.