pycycle-mcpby Design Research Collective, Carnegie Mellon University (cmudrc)
An MCP server for pyCycle engine-cycle models built on OpenMDAO: run cycles, sweep inputs and evaluate total derivatives.
There is no general OpenMDAO MCP server. The one listing, pycycle-mcp from Carnegie Mellon's Design Research Collective, covers pyCycle engine-cycle models built on OpenMDAO: it manages cycles, updates variables, runs sweeps and evaluates total derivatives, and feeds thrust and fuel burn into a CPACS aircraft pipeline. The OpenMDAO team publishes no AI integration. For other OpenMDAO problems, an agent has to write and run the Python itself.
An MCP server for pyCycle engine-cycle models built on OpenMDAO: run cycles, sweep inputs and evaluate total derivatives.
Listings are sorted by origin, then by recent activity. GitHub data is refreshed nightly. Nothing here is ranked.
An MCP server or skill can only do what OpenMDAO lets programs do. OpenMDAO exposes 2 automation interfaces:
The OpenMDAO site and documentation cover the framework, its components, solvers and derivatives, but no MCP server or AI assistant as of this check. The pyCycle server comes from a university group that also publishes MCP servers for SU2, TiGL geometry and mission analysis as part of a shared CPACS aircraft-analysis pipeline.
Checked 4 Nov 2026. Sources: OpenMDAO documentation, cmudrc/pycycle-mcp README
Taken from the listings' own documentation. Check each listing for exactly what it supports.
Not for OpenMDAO in general. pycycle-mcp covers pyCycle engine-cycle models, which are built on OpenMDAO; for other models the agent writes and runs OpenMDAO Python directly.
The Design Research Collective at Carnegie Mellon University, under the MIT licence. It is one of several servers (SU2, TiGL, mission segments, Aviary) that share a CPACS aircraft file in their pipeline.
Real cycle runs do. The repository's examples and tests are deterministic stand-ins, so development and CI work without the full pyCycle and OpenMDAO runtime. It needs Python 3.12 or later.
Its adapter reads engine data from the vehicles/engines branch and the aerodynamic drag coefficient from the aero results, runs a turbofan cycle, and writes design and off-design net thrust, TSFC, OPR, BPR and fuel flow to an mcpResults node under each engine.
Not through a dedicated server. OpenMDAO models are Python, so an agent with a general code-execution tool can write components, groups and drivers, but there is no MCP server that validates or runs arbitrary OpenMDAO problems.
AI-generated models, drawings and results must be checked by a qualified engineer before use.
Sources (checked 4 Nov 2026): OpenMDAO documentation · OpenMDAO/pyCycle repository · cmudrc/pycycle-mcp README · OpenMDAO product page
OpenMDAO is a trademark of NASA. Tresca is independent and not affiliated with or endorsed by NASA.