Ansys AEDT MCP (CAE Agent Hub)
MCP serverCommunity
A 45-tool AEDT server in the CAE Agent Hub that mirrors PyAEDT-MCP's tool names and adds Maxwell tools and explicit session targeting. By Cai-aa.
1.3k starsUpdated 10 days agoGitHub data from 5 Nov 2026
At a glance
- Type
- MCP server
- Works with
- Ansys HFSS / Maxwell
- How it connects
- Drives a running copy of the tool
- Access
- Can modify models
- Tool versions
- AEDT 2026 R1 (default and live-tested target); pins PyAEDT 1.5.0
- Operating systems
- Windows
- Needs a Ansys HFSS / Maxwell licence
- Yes
- Transport
- Local (stdio)
- AI clients documented
- Codex
- Licence
- MIT
- Language
- Python
What it can do
- Uses the same core tool names as Ansys's official PyAEDT-MCP, from launching and connecting to validating, solving and exporting results.
- Requires an explicit AEDT process ID or gRPC port on every call, so it never acts on the wrong window, and keeps one PyAEDT broker per target outside AEDT.
- Adds 15 Maxwell tools for coil terminals, windings, motion bands, force and torque, eddy effects and field plots.
- Includes an Icepak safe mode that submits single-core solves and exports residual and mesh evidence to CSV.
Limitations
- Live-tested on AEDT 2026 R1 only.
- A started analysis is only a submission; the agent must confirm completion separately.
- Motion tools assign an existing band but don't build or check the surrounding geometry.
Install
py -3.10 -m venv .venv
.\.venv\Scripts\python.exe -m pip install -U pip
.\.venv\Scripts\python.exe -m pip install -e .Source: github.com/Cai-aa/CAE-Agent-Hub/tree/main/MCP/Ansys/AEDT%20MCP
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.