CST Studio Orchestrator MCP
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.
README
CST Studio Orchestrator MCP
An open-source Model Context Protocol (MCP) server that turns CST Studio Suite into a unified AI-controllable simulation environment.
This project exposes CST Studio Suite to AI agents and automation clients. It supports 3D electromagnetic modeling, antenna and RF workflows, solver setup, result extraction, PCB/SI helpers, and direct CST Design Studio schematic control for field-circuit co-simulation through project.schematic.
Highlights
- 177 MCP tools for CST automation across modeling, antennas, materials, ports, mesh, solvers, simulation, results, PCB/SI, optimization, VBA, and schematic workflows.
- Connected mode on Windows with CST Python libraries for live control of CST Studio Suite.
- Offline mode for generating CST VBA scripts when CST is not available.
- Design Studio schematic tools for RLC components, external ports, net connections, schematic inspection, object discovery, and generic RemoteObject calls.
- Generic schematic bridge for CST's runtime
project.schematicinterface, including objects such asBlock,Net,ExternalPort,CircuitProbe,SchematicLayout,SimulationTask,ParameterSweep, andOptimizer. - Built-in CST VBA reference data and guardrails for raw VBA execution.
Why This Exists
Most CST automation examples focus on 3D Microwave Studio history commands. CST Design Studio and schematic workflows are less visible because schematic actions do not reliably appear in the 3D History List.
This fork adds a practical bridge for Design Studio:
project.schematic.Block
project.schematic.Net
project.schematic.ExternalPort
project.schematic.SchematicLayout
On CST Studio Suite 2025.2, the generic schematic tools can enumerate 125 project.schematic members and call methods on runtime remote objects directly.
Schematic Tools
Specialized tools:
cst_schematic_create_rlccreates a resistor, inductor, or capacitor.cst_schematic_create_external_portcreates a schematic external port.cst_schematic_connectconnects block or port pins into a named net.cst_schematic_listlists schematic blocks and nets.
Generic bridge tools:
cst_schematic_list_objectslists public members exposed byproject.schematic.cst_schematic_object_methodslists methods on one schematic object.cst_schematic_callcallsproject.schematic.<object_name>.<method_name>(*args, **kwargs).
Example generic call:
{
"object_name": "Block",
"method_name": "GetNumberOfPorts",
"args": []
}
Installation
git clone https://github.com/guardianer9-debug/cst-studio-orchestrator-mcp.git
cd cst-studio-orchestrator-mcp
pip install -e ".[dev]"
MCP Configuration
{
"mcpServers": {
"cst-studio-orchestrator": {
"command": "cst-studio-orchestrator-mcp",
"env": {
"CST_PATH": "D:\\CST2025",
"CST_WORK_DIR": "D:\\cst_projects",
"PYTHONPATH": "D:\\CST2025\\AMD64\\python_cst_libraries"
}
}
}
}
The legacy command names mcp-cst-studio and cst-field-circuit-mcp are also kept for compatibility.
Connected Mode
Connected mode requires:
- Windows
- CST Studio Suite installed
- CST Python libraries available on
PYTHONPATH - Python 3.10+
Example:
$env:PYTHONPATH="D:\CST2025\AMD64\python_cst_libraries;$env:PYTHONPATH"
python -c "import cst.interface; print('CST available')"
cst-studio-orchestrator-mcp
Offline Mode
When CST is unavailable, most modeling tools return VBA scripts that can be run manually in CST Studio Suite. The generic schematic reflection tools require connected mode because they depend on CST runtime remote objects.
Development
pip install -e ".[dev]"
pytest -q
ruff check src tests
Current local validation:
535 passed
ruff: All checks passed
Project Lineage
This project is derived from RFingAdam/mcp-cst-studio and keeps the original AGPL-3.0-or-later license. This fork adds CST Design Studio schematic automation and a generic project.schematic RemoteObject bridge for broader CST Studio Suite orchestration, including antennas, RF/EM workflows, PCB/SI, and field-circuit co-simulation.
See NOTICE for attribution details.
License
AGPL-3.0-or-later. CST Studio Suite itself is a separate commercial product from Dassault Systemes/SIMULIA and is not bundled or redistributed by this project.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.