ANSYS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWP_ROOT242 | Yes | ANSYS 安装路径（如 C:\Program Files\ANSYS Inc\v242） |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fluent_launchC | Launch Fluent or attach to a gRPC instance. |
| fluent_read_caseB | Read an existing Fluent case file. |
| fluent_read_meshB | Read an existing Fluent mesh file. |
| fluent_set_solverA | Configure viscosity, energy, and steady/transient solver settings. |
| fluent_set_boundaryC | Set one boundary type and validated properties. |
| fluent_set_materialB | Assign a material to a Fluent cell zone. |
| fluent_initializeC | Initialize the Fluent solution. |
| fluent_iterateC | Run Fluent solver iterations. |
| fluent_get_residualsA | Read the latest Fluent residual values. |
| fluent_saveA | Write Fluent case and data using a path prefix. |
| fluent_tuiB | Execute arbitrary Fluent TUI after explicit unsafe confirmation. |
| fluent_statusA | Return connection and version state without modifying Fluent. |
| fluent_load_udfA | Compile or interpret an existing Fluent UDF source file. |
| fluent_hook_udfB | Attach a loaded UDF profile to a boundary field. |
| fluent_list_udfsB | List detected UDF profile hooks. |
| fluent_exitA | Detach from Fluent or close an MCP-launched instance. |
| fluent_get_scriptA | Return only the current session's generated Fluent journal. |
| fluent_get_mapping_reportA | Return structured MCP-to-TUI mapping history. |
| fluent_reset_mapperA | Clear the current Fluent session's mapping history. |
| mechanical_launchB | Launch Mechanical batch mode or attach to an existing gRPC instance and probe readiness. |
| mechanical_importA | Import an existing geometry file into the active Mechanical model. |
| mechanical_set_materialB | Assign a material to exactly one named body. |
| mechanical_meshB | Configure mesh size and method, then optionally generate the mesh. |
| mechanical_get_mesh_settingsA | Read configured global mesh settings and generated counts. |
| mechanical_apply_loadB | Apply one typed load or support to one uniquely named selection. |
| mechanical_solveB | Solve the active Mechanical model. |
| mechanical_get_resultC | Read an existing result or optionally create and evaluate one. |
| mechanical_listB | List bodies, named selections, or analyses. |
| mechanical_scriptA | Execute arbitrary Mechanical IronPython after explicit unsafe confirmation. |
| mechanical_statusA | Return transport, scripting, project, model, and analysis readiness. |
| mechanical_exitA | Detach from Mechanical or close an MCP-launched instance. |
| geometry_launchC | Launch a Geometry service for Discovery or SpaceClaim. |
| geometry_create_designB | Create and select a new Geometry design. |
| geometry_create_blockB | Create a centered block using SI length units. |
| geometry_create_cylinderB | Create a centered cylinder using SI length units. |
| geometry_create_sphereA | Create a centered sphere using SI length units. |
| geometry_exportA | Export the active design to the exact requested STEP or IGES path. |
| geometry_list_bodiesA | List bodies in the active Geometry design. |
| geometry_import_fileA | Insert an existing CAD file into the active design. |
| geometry_statusA | Return Geometry connection and active-design state. |
| geometry_closeA | Close the MCP-launched Geometry service. |
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 41 tools
Domain prefixes (geometry_, mechanical_, fluent_) clearly separate tools, and within each domain actions like apply_load, solve, and get_result are distinct. The only potential overlap is between geometry_import_file and mechanical_import, but their descriptions clarify the active model.
Tool names follow a domain_verb_noun snake_case pattern, which is predictable. However, retrieval verbs vary ('list', 'get', 'read') and lifecycle verbs differ ('close' for geometry, 'exit' for mechanical/fluent), creating minor inconsistency.
With 41 tools, the server exceeds the 25+ threshold for 'too many' and may overwhelm agents. While the broad scope (Geometry, Mechanical, Fluent) justifies some size, the count is still heavy and would benefit from consolidation.
Core workflows are covered: geometry creation/import/export, mechanical setup/solve/result, and fluent setup/solve/save. Minor gaps exist, such as no geometry editing/deletion and limited result types, but these are workable for typical simulation tasks.