ANSYS Mechanical & ACP MCP Servers

MCP serverCommunity

Connects to a running Mechanical 2026 R1 session over PyMechanical gRPC with named tools for materials, mesh, loads, solve and results. By codersag.

20 starsUpdated 13 days agoGitHub data from 5 Nov 2026

At a glance

Type: MCP server
Works with: Ansys Mechanical / MAPDL
How it connects: Drives a running copy of the tool
Access: Can modify models
Tool versions: Ansys Mechanical 2026 R1 (v261) only; ACP server tested with ACP 2026 R1
Operating systems: Windows
Needs a Ansys Mechanical / MAPDL licence: Yes
Transport: Local (stdio)
AI clients documented: Claude Desktop, Cursor, Windsurf, VS Code (GitHub Copilot), Continue
Licence: Apache-2.0
Language: Python

Provides dedicated tools for materials, mesh sizing, contacts, supports and loads, nonlinear settings, solving, result objects, named selections and point masses.
Reads back every object it creates and rolls it back if a later step fails; results added before a solve are flagged as unsolved rather than reported as zero.
Exports nodal results, linearizes stress along a path and writes TXT or DOCX reports with optional extras.
Ships a second server for building composite layups in Ansys Composite PrepPost through PyACP.

Only Mechanical 2026 R1 has been exercised; older releases are untested and may lack API members.
You start Mechanical's gRPC server yourself from a Workbench script and pass the port.
The free-form Mechanical script tool is off by default.
Its command is also named ansys-mechanical-mcp, the same as Ansys's official PyMechanical-MCP package, so don't install both into one Python environment.

git clone https://github.com/codersag/mechanical-mcp.git
cd mechanical-mcp
pip install -e .

{
  "mcpServers": {
    "mechanical-mcp": {
      "command": "ansys-mechanical-mcp"
    }
  }
}

MCP servers and skills run code on your computer. Review the source before installing.

AI-generated models, drawings and results must be checked by a qualified engineer before use.