Skip to main content
Glama

Related Servers

Alternatives to CST-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Python-first MCP server for CST Studio Suite (2024–2026) that lets AI assistants drive CST from Windows: open projects, build geometry, set materials and ports, run solvers, read S-parameters and farfield metrics, and generate design reports.
      184
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables safe, audited automation of CST Studio Suite 2026.2 by inspecting projects, building models from structured parameters and fixed History templates, running periodic unit-cell solves, and computing R/T/A and PCR from saved complex channels with CSV, HTML, and Touchstone export. Writes are confined to a work directory, mutations and solver actions require explicit confirmation, and unresolved solver outcomes are blocked rather than reported as success.
      Apache 2.0
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that integrates CST Studio Suite with the Model Context Protocol to enable automated electromagnetic simulation workflows. It provides specialized tools for material definition management and direct interaction with the CST Studio Suite environment.
      35
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language-driven modeling, simulation, and optimization of antennas in CST Studio Suite, covering geometry, materials, ports, solvers, S-parameters, far-field analysis, parameter sweeps, and optimization via 73 MCP tools.
      MIT

    TDQS

    C2.4/5.0

    Scored across 84 tools

    Disambiguation2/5

    Several tools are explicit aliases or overlapping dispatch mechanisms (e.g., cst_runtime_detect_tool / cst_toolbox_detect_tool, cst_runtime_invoke_tool / cst_toolbox_invoke_tool, plus cst_call_tool and cst_run_vba_tool). While many geometry and solver tools are distinct, the runtime/toolbox/meta families create real confusion about which tool to call.

    Naming Consistency4/5

    Almost all tools follow a consistent cst_ prefix, snake_case, and _tool suffix pattern. The main deviation is the runtime vs. toolbox alias naming, which is still readable and predictable.

    Tool Count1/5

    With 84 tools, this server is far beyond the typical well-scoped range. The count is inflated by duplicate aliases and meta/runtime wrappers, making the surface heavy and hard to manage.

    Completeness4/5

    The tool set covers project lifecycle, geometry creation, materials, ports, boundaries, solver configuration, results reading, sweeps, and exports broadly. Some operations such as mesh generation are explicitly unsupported, leaving minor gaps rather than major dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues