Skip to main content
Glama
rhyne1012

OpenVSP MCP (Maintained Fork)

Related Servers

Alternatives to OpenVSP MCP (Maintained Fork)

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools for CPACS-oriented TiGL workflows, enabling lifecycle management, inspection, export, and parameter manipulation of aircraft geometry models without native geometry runtimes.
      3
      MIT
    • A
      license
      A
      quality
      A
      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.
      10
      GPL 2.0
    • F
      license
      A
      quality
      B
      maintenance
      CAD-engineering MCP tool server for parametric modeling, DFM validation, mechanical calculations, and more. Enables code-CAD builds (build123d/CadQuery), model inspection, meshing, and mechanical calculators via MCP stdio.
      11
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides pre-flight validation and post-processing tools for OpenMC Monte Carlo transport simulations, catching common authoring mistakes before jobs hit the HPC queue.
      MIT

    TDQS

    B3.1/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools occupy clearly distinct lifecycle roles: health, batch management, model creation/editing, preflight, analysis, and result reading. The only mild ambiguities are modify vs. set_parameters and run_vspaero vs. sweep vs. batch_submit, but the descriptions do enough to separate them.

    Naming Consistency3/5

    Names use consistent snake_case, but grammatical styles are mixed: batch_* is noun-first, most other tools are bare verbs or verb_noun, and health is a standalone noun. The conventions are still readable and group-related tools are predictable, but the pattern is not uniform.

    Tool Count4/5

    Sixteen tools is slightly above the typical 3-15 range, but each tool serves a meaningful purpose and the set is organized into clear clusters. The count feels justified for a full OpenVSP workflow rather than bloated.

    Completeness5/5

    The tool surface covers the core model lifecycle, parameter editing, preflight checks, single and sweep analysis, batch job submission/control/export, and result reading. Batch operations are especially complete with submit, status, cancel, resume, and export, leaving no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues