ansys-mechanical-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mechanical_statusA | [READ ONLY] Report MCP and Mechanical connection state. |
| connect_mechanicalA | [READ ONLY] Connect to the configured local Mechanical server. |
| get_project_infoB | [READ ONLY] Inspect Mechanical model data. |
| get_model_summaryA | [READ ONLY] Inspect Mechanical model data. |
| get_geometry_bodiesC | [READ ONLY] Inspect Mechanical model data. |
| get_material_assignmentsC | [READ ONLY] Inspect Mechanical model data. |
| get_connectionsC | [READ ONLY] Inspect Mechanical model data. |
| get_named_selectionsB | [READ ONLY] Inspect Mechanical model data. |
| get_boundary_conditionsC | [READ ONLY] Inspect Mechanical model data. |
| get_mesh_statisticsB | [READ ONLY] Inspect Mechanical model data. |
| get_messagesC | [READ ONLY] Inspect Mechanical model data. |
| get_solution_statusB | [READ ONLY] Inspect Mechanical model data. |
| get_result_summaryC | [READ ONLY] Inspect Mechanical model data. |
| get_treeA | [READ ONLY] Return a bounded model-tree hierarchy. |
| capture_model_imageA | [READ ONLY] Capture the current Mechanical graphics view. |
| open_projectB | [MODIFIES MODEL] Open a Mechanical project/database file. |
| set_material_assignmentB | [MODIFIES MODEL] Assign a material to one uniquely named body. |
| create_named_selectionB | [MODIFIES MODEL] Create a geometry named selection from entity IDs. |
| set_mesh_sizeB | [MODIFIES MODEL] Set the global mesh element size with units. |
| generate_meshB | [MODIFIES MODEL] Generate the Mechanical mesh. |
| set_loadC | [MODIFIES MODEL] Set components on one existing named load. |
| solve_analysisD | [SOLVES ANALYSIS] Solve one uniquely named analysis. |
| evaluate_resultsB | [MODIFIES MODEL] Evaluate all existing results in an analysis. |
| save_project_asB | [WRITES FILE] Save a copy beneath the configured output directory. |
| workbench_statusA | [READ ONLY] Report Workbench batch-runner configuration. |
| inspect_workbench_projectB | [READ ONLY] Enumerate systems and cells in a saved Workbench project. |
| audit_workbench_mechanical_systemC | [READ ONLY] Audit an existing Mechanical system through its Workbench Model container. |
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 27 tools
Most tools have clearly distinct targets (mesh, materials, loads, results) with a consistent get_/set_ pattern. A few like get_project_info, get_model_summary, and get_tree might overlap in purpose, but descriptions likely clarify. Overall, an agent can reliably select the right tool with minimal confusion.
The majority follow a verb_noun pattern (get_, set_, open_, generate_, solve_, save_). However, 'mechanical_status' breaks the pattern by leading with a noun, and 'workbench_status' similarly deviates. Minor inconsistencies exist but overall the naming is readable and predictable.
At 27 tools, the surface exceeds the 25-tool threshold typically considered too heavy. However, for a complex engineering simulation server, the breadth might be justified. Still, it feels slightly over-scoped, especially with many similar get_ inspection tools.
The tool set covers the full lifecycle from connection and model inspection through modification, solving, results evaluation, and saving, plus Workbench integration. Minor gaps like advanced geometry editing or result post-processing beyond summary exist, but core workflows are well supported.