Skip to main content
Glama
ismailakdag

cst-studio-mcp

by ismailakdag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to cst-studio-mcp

No user-submitted related servers found.

    Related Servers

    • CST-MCP

      woson-L
      A
      license
      C
      quality
      B
      maintenance
      Enables an MCP client to drive CST Studio Suite 2026 through its official Python automation API, covering 3D modelling, materials, ports, boundaries, mesh and solver configuration, solver runs, and result reading. Also provides verification and export tools — S11, reference impedance, port diagnostics, energy budget and model audit — plus Touchstone/ASCII/JSON evidence output and parameter sweeps, all locally over stdio.
      84
      MIT

    • cst-mcp

      AndersOnLin4
      A
      license
      Not graded
      quality
      A
      maintenance
      Turns CST Studio Suite into an AI-controllable electromagnetic design lab, enabling conversational THz metamaterial absorber design, unit-cell automation, Floquet port control, batch solve with checkpoint-resume, and surrogate-model predictions.
      2
      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

    • cst-agent

      K-13ROBOT
      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
    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

    B3.3/5.0

    Scored across 184 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes across geometry, simulation, results, and antenna/PCB domains. A few near-overlaps exist (e.g., cst_get_farfield vs cst_get_radiation_pattern_3d, cst_run_simulation vs cst_workflow_run_and_s11) but descriptions sufficiently differentiate them.

    Naming Consistency3/5

    All tools share the cst_ prefix, but the pattern mixes verb-based names (cst_create_brick, cst_get_s_parameters) with category-based names (cst_antenna_patch, cst_pcb_create_trace, cst_matching_l_network). Within each category naming is consistent, but globally it is a mixed convention.

    Tool Count1/5

    184 tools is extreme over-proliferation. Even the lower bound of 'too many' (25+) is far exceeded, creating an overwhelming surface that increases selection difficulty and maintenance overhead.

    Completeness5/5

    The domain coverage is remarkably thorough: project management, geometry creation, materials, ports, boundaries, mesh, solvers, simulation control, results extraction, antenna templates, arrays, PCB design, matching networks, and workflows. No significant gaps are apparent for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources