aalperakiss/acp-mcp-agent

MCP server for ACP(Pre) -lay-up read/edit, rule checks and export, headless via PyACP or live in the GUI.

About acp-mcp-agent

An MCP server that lets an LLM agent drive ANSYS Composite Pre [ACP(Pre)] — read a lay-up, change fibre angles and layer counts, check manufacturing rules, and export the analysis model and composite definitions.

It talks to ACP two ways, and the difference matters:

PyACP launches its own headless ACP session and cannot attach to a running ACP-Pre window. So a second path exists: a small socket listener running inside the GUI's embedded Python, which executes model edits on the wx main thread. Angles change and the viewport redraws while you watch.

The two sessions are independent. acpgui edits the model open in the GUI; acp edits the headless one. Pick one per task and stay there.

Scope is the upstream half of the composites loop. Solve and post-processing stay where they already work:

------ ANSYS with ACP. Developed and tested with 2026 R1 (AWPROOT261) Python 3.10+ for the server side — whichever interpreter your MCP client launches Packages mcp, pydantic, ansys-acp-core (see requirements.txt) OS Windows. The bridge itself is portable, the documented paths are not Client Any MCP client. Verified with Claude Desktop

ANSYS is not a pip package. ansys-acp-core starts the ACP gRPC server from a local ANSYS installation; without one, nothing here runs.

The GUI bridge needs nothing installed: it runs inside ACP-Pre's own embedded Python (3.10 on tested-2026 R1) and uses only the standard library plus wx, which ACP-Pre already provides.

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/aalperakiss--acp-mcp-agent.html)

Related MCP servers