Skip to main content
Glama
LaplaceYoung

ansys-aedt-mcp

by LaplaceYoung
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ansys-aedt-mcp

No user-submitted related servers found.

    Related Servers

    • COMSOL MCP Server

      HBPEKING-TKS
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization through the MCP protocol.
      78
      MIT

    • comsol-mcp-server

      Qwup2112
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization via the MCP protocol.
      MIT

    • HFSS MCP Server

      whatever1takes
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for automating ANSYS HFSS simulations, enabling persistent connections, modeling, simulation setup, and S-parameter extraction through AI assistants.
      1
      -

    • CST Studio Orchestrator MCP

      guardianer9-debug
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to control CST Studio Suite for 3D electromagnetic simulation, antenna design, and schematic-based field-circuit co-simulation through 177 MCP tools.
      100
      6
      AGPL 3.0

    • COMSOL MCP Server

      wjc9011
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to automate multiphysics simulations in COMSOL Multiphysics, covering model management, geometry building, physics configuration, and results visualization. It supports complex simulation workflows through the MCP protocol and includes integrated knowledge retrieval for documentation and troubleshooting.
      93
      755
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.4/5.0

    Scored across 109 tools

    Disambiguation2/5

    Many tools have overlapping purposes, especially the generic escape hatches: aedt_run_app_method, aedt_call, aedt_batch_call, aedt_native_module_call, and aedt_native_module_batch_call all expose similar 'call any method' behavior in slightly different contexts. Specific operations also blur boundaries, e.g. aedt_hfss_operation vs aedt_assign_boundary_or_excitation vs aedt_create_port, making it hard for an agent to confidently select the right tool.

    Naming Consistency5/5

    Tool names consistently follow an aedt_ prefix with snake_case and a verb_noun pattern (create_, get_, set_, list_, export_, import_, update_, analyze_). Even compound nouns like aedt_source_port_summary and aedt_optimetrics_setup_operation remain predictable, and there is no mixing of conventions.

    Tool Count1/5

    109 tools is an extreme count for any MCP server, far exceeding the 25+ threshold for poor scoping. While the AEDT domain is broad, this many tools creates a massive selection space that will overwhelm agents and defeat the purpose of a curated tool surface.

    Completeness4/5

    The tool surface is unusually broad, covering projects, designs, setups, sweeps, boundaries, materials, meshing, post-processing, exports, and native API access. The generic fallback tools (aedt_call, aedt_batch_call) ensure no operation is a hard dead end, though some specialized workflows still depend on those generic calls rather than purpose-built tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources