Skip to main content
Glama

Related Servers

Alternatives to openmdao-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to build, validate, calibrate, and export versioned scientific models with mandatory units, dimensional and numerical checks, and uncertainty analysis over stdio. Models can be simulated and exported to portable formats such as SBML, CellML, and Modelica.
      59 npm
      9
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables running reproducible AVL 3.52 aerodynamic analyses through MCP, with input validation, isolated execution, sweeps, background jobs, and structured results including solver files.
      14
      GPL 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients and LLM agents to run deterministic fast-reactor and fuel-cycle solvers in one place: sodium bundle thermal hydraulics with FCCI margins, RVACS decay-heat transients, heat-pipe/sCO2 capillary limits, LiCl-KCl electrorefining mass balance, Ac-225 isotope yield, data-center microgrid load-following, defense microreactor resilience, and HALEU cask logistics. Exposes a chained multi-physics transient orchestrator tool alongside a standalone CLI for scripted physics runs.
      11
      Academic Free v1.1
    • A
      license
      C
      quality
      B
      maintenance
      Enables natural-language automation of LS-PrePost preprocessing and postprocessing by exposing tools that build and verify shell meshes, query nodes, parts and connectivity, run native commands, SCL and in-application Python, and read d3plot/binout results through pluggable backends. Every job runs in its own directory and returns an ID, status, log and artifacts, so results stay traceable and failures are never silently reported as success.
      30
      MIT

    TDQS

    A3.5/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools map to distinct lifecycle stages, and the descriptions clearly separate problem creation, update, loading, and execution. There is minor conceptual overlap between related execution tools such as run_driver, run_doe, and run_multistart, and between list_variables and get_outputs, but their intended uses are still recoverable.

    Naming Consistency5/5

    Tool names consistently use lowercase snake_case with an action verb first: get_, create_, update_, load_, list_, configure_, run_, compute_, check_, query_, and export_. The lone single-verb tool, ping, is a standard health-check name and does not meaningfully break the pattern.

    Tool Count4/5

    At 21 tools the surface is somewhat heavy, but the OpenMDAO workflow legitimately spans problem management, configuration, execution, derivative analysis, case querying, and visualization. Each tool appears to correspond to a meaningful operation rather than duplicating another, though the specialized run and check tools push the count above the typical range.

    Completeness5/5

    The tool set covers the full lifecycle: create/update/load/list/close problems, retrieve specs, inspect variables, set inputs, configure solvers/optimization/approximations, run models/drivers/DOE/multistart, compute and verify totals, query recordings, export N2 diagrams, and health-check the server. Deletion is handled through close_problem with delete_files, so there are no obvious dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues