PyAEDT-MCP is an MCP (Model Context Protocol) server for Ansys Electronics Desktop (AEDT). It gives you reliable AEDT tools and a persistent PyAEDT-backed Python session for tasks that do not fit a dedicated tool.
What PyAEDT-MCP does
PyAEDT-MCP supports this runtime loop:
- Check whether AEDT is installed or already reachable.
- Launch AEDT or connect to an existing gRPC session.
- Open projects, create designs, run analyses, inspect the model, and export results.
- Use
run_python_codeorrun_python_scriptfor custom PyAEDT work.
Supported AEDT applications include HFSS, Maxwell 2D/3D, Q2D, Q3D, Icepak, Circuit, TwinBuilder, Mechanical, EMIT, RMXprt, and HFSS 3D Layout.
Install
Run without cloning
Install uv and
Git first. Git is required because uvx
downloads and runs PyAEDT-MCP directly from this repository without cloning it.
uvx --from git+https://github.com/ansys/pyaedt-mcp.git ansys-aedt-mcp
Install locally
pip install git+https://github.com/ansys/pyaedt-mcp.git
Or use uv:
uv pip install git+https://github.com/ansys/pyaedt-mcp.git
Windows installer
Windows releases include PyAEDT-MCP-Installer-windows.exe:
- Installs the desktop manager into
C:\Program Files\ANSYS Inc\PyAEDT MCP. - Adds a Start Menu entry and registers an uninstaller in Windows Installed Apps.
- On first use, creates
%APPDATA%\.pyaedt_mcp\.venvand uses bundled CPython 3.13 anduvto installansys-aedt-mcpfrom PyPI. - Supports offline installation from the Settings tab. Each install or update prompts you to select a Python 3.13 wheelhouse ZIP and installs only from that archive, without querying package indexes.
- Saves the offline installation selection in
%APPDATA%\.pyaedt_mcp\settings.yaml.
Opening the executable provides setup, HTTP server controls, AEDT options, and stdio or HTTP profiles for Copilot/VS Code, Claude, Cursor, Codex, and OpenCode.
Install for development
git clone https://github.com/ansys/pyaedt-mcp.git
cd pyaedt-mcp
pip install -e .
pre-commit install
Or use uv:
git clone https://github.com/ansys/pyaedt-mcp.git
cd pyaedt-mcp
uv pip install -e .
pre-commit install
Requirements
- Python 3.12 or later
- Git to install or run PyAEDT-MCP directly from this repository with
uv - AEDT 2022 R2 or later for gRPC workflows
- A local AEDT installation or a reachable remote AEDT gRPC endpoint
Quick start
-
Start AEDT in gRPC mode when connecting to an existing session:
"C:\Program Files\ANSYS Inc\v261\AnsysEM\ansysedt.exe" -grpcsrv 50051
Or, just launch AEDT normally. It automatically starts a gRPC server.
PyAEDT-MCP can also launch AEDT for you if it is not already running.
-
Choose an MCP transport:
- stdio is the simplest option for one local client. The client starts
PyAEDT-MCP automatically through
uvxor from a cloned repository's virtual environment. - HTTP connects the client to a separately running server. Use it for local development, Docker, or a remote server.
Start an HTTP server through
uvxwithout cloning:uvx --index-strategy unsafe-best-match \ --from git+https://github.com/ansys/pyaedt-mcp.git ansys-aedt-mcp \ --transport http --http-host 127.0.0.1 --http-port 8080
- stdio is the simplest option for one local client. The client starts
PyAEDT-MCP automatically through
-
Point an MCP client at the server:
Use the IDE and client configuration guide for short HTTP and stdio configurations for VS Code/Copilot, Claude, OpenCode, and Codex, plus local virtual-environment instructions.
Tool reference
For information on the available tools, see Tools and capabilities in the PyAEDT-MCP documentation.
How the repository is organized
The core package is in src\ansys\aedt\mcp:
| File | Role |
|---|---|
__main__.py |
Module entry point that forwards to the CLI launcher |
server.py |
CLI parsing, app setup, context creation, startup cleanup, and transport selection |
tools.py |
Runtime tool implementations for AEDT lifecycle, project, scripting, and export workflows |
helpers.py |
Small utilities for probing endpoints, normalizing versions, and extracting model data |
prompts.py |
System prompt content shown to MCP clients |
contexts.py |
Optional context helper tools enabled by --include-context |
toolsets.py |
toolsets://definition resource used for logical tool discovery |
aedt_helper\startup_code.py |
Startup code loaded into the persistent Python session |
Other top-level folders include:
doc\source: Sphinx documentationtests: Unit and integration coveragedocker: Container assetsexamples: Sample assets used by the project
Development workflow
To contribute, see Contribute in the PyAEDT-MCP documentation.
Add a new tool
Most tools require a live AEDT connection. Tag those tools with REQUIRES_AEDT_TAG in src\ansys\aedt\mcp\tools.py so they can be hidden until the session exists when dynamic discovery is enabled.
For more information, see Add a new tool in the PyAEDT-MCP documentation.
License
Apache 2.0 license. See LICENSE.
Related projects
Release files for ansys-aedt-mcp 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ansys_aedt_mcp-0.2.3.tar.gz | 48.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansys_aedt_mcp-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 101.1 kB
Release files / ansys_aedt_mcp-0.2.3.tar.gz
| Download URL | ansys_aedt_mcp-0.2.3.tar.gz |
|---|---|
| Size | 48.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cda8670fd136bc1cb3c39b38ab0134747276eb2e7a2ce7e559dcbd2942b5e610
|
|
BLAKE2b-256 checksum How to use checksums |
b5a8bd451b32722dbf4aff9449382bd57b62327c6d3c6fb37870927932b465e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logRelease files / ansys_aedt_mcp-0.2.3-py3-none-any.whl
| Download URL | ansys_aedt_mcp-0.2.3-py3-none-any.whl |
|---|---|
| Size | 52.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63cd7e8e4cd0636f74797e1c6e5f4b5f9ca748306733028363bef99d660638de
|
|
BLAKE2b-256 checksum How to use checksums |
a587ba561e8ee6abfa0f026e3752aa6ea58765daf7065ea37c3261a72c5ed98b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency log