PyAEDT-MCP
Related Servers
Alternatives to PyAEDT-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Codex to control Ansys Workbench and ICEM CFD locally, executing scripts, managing projects, and running simulations.1MIT
- AlicenseCqualityDmaintenanceEnables AI agents to control Ansys Electronics Desktop (HFSS, Maxwell, Q3D, etc.) using MCP tools for simulation automation.10063PolyForm Noncommercial 1.0.0
- AlicenseCqualityCmaintenanceEnables MCP-capable AI clients to connect to local ANSYS Mechanical and Workbench for read-only inspection and bounded model, material, load, mesh, solve, result, and save operations via PyMechanical/gRPC.27MIT
- FlicenseNot gradedqualityDmaintenanceA clean MCP server and ACT extension for controlling ANSYS Workbench and ANSYS Mechanical from any MCP client, enabling launching Workbench journals, executing Mechanical Python scripts, and interacting with a running Mechanical session via file queue or socket timer bridge.2-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Ansys simulation software (Fluent, MAPDL, Mechanical, Geometry) through the Model Context Protocol.71MIT
- AlicenseBqualityCmaintenanceEnables an MCP-compatible AI client to control CADFEKO, the FEKO solver, and POSTFEKO by running Lua API scripts, launching asynchronous jobs, tracking progress, and exporting S11, impedance, Touchstone, model files, and images.9MIT
TDQS
Scored across 21 tools
Most tools target a distinct resource+action, and descriptions clarify boundaries like launch_aedt vs connect_to_aedt, and check_aedt_installed vs check_aedt_status. Overlap remains in a few spots: list_designs also returns projects (overlapping list_projects), get_model_info overlaps check_aedt_status's project/design reporting, and run_python_script vs run_python_code differ only subtly in execution context.
Nearly all tools follow a clean snake_case verb_noun pattern (launch_aedt, list_projects, create_design, export_results, validate_design). The only deviation is the bare noun 'screenshot', which breaks the otherwise predictable pattern.
21 tools is on the higher side but each maps to a real capability across connection lifecycle, project/design management, script execution, and reporting. The set is somewhat broad, with display_html being peripheral to the core AEDT workflow, but nothing feels redundant filler.
Core workflows (launch/connect, project open/save, design create/validate/analyze, results export, script execution) are covered. However there are notable asymmetries: no create_project or close_project, no delete operations for projects/designs, and export_config has no matching import_config, leaving agents with dead ends for common lifecycle steps.