Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Related Servers

Alternatives to PyAEDT-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Codex to control Ansys Workbench and ICEM CFD locally, executing scripts, managing projects, and running simulations.
      1
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables 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.
      27
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A 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
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      9
      MIT

    TDQS

    B3.3/5.0

    Scored across 21 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data