Skip to main content
Glama
rhyne1012

OpenVSP MCP (Maintained Fork)

by rhyne1012
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to OpenVSP MCP (Maintained Fork)

No user-submitted related servers found.

    Related Servers

    • tigl-mcp

      cmudrc
      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

    • avl-mcp

      rhyne1012
      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.
      11
      GPL 2.0

    • root-ext-cad

      graphgrow
      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
      -

    • openmc-validator-mcp

      zxkjack123
      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
    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

    A4.3/5.0

    Scored across 16 tools

    Disambiguation4/5

    Descriptions meticulously cross-reference each other and carve out boundaries (preview/inspect/query, run_vspaero/sweep/batch_submit, set_parameters/modify, preflight/health), which strongly aids selection. However, genuine overlap remains between the edit tools (set_parameters vs modify) and the solving tools, requiring careful reading to distinguish rather than being self-evident.

    Naming Consistency4/5

    All tools share a consistent openvsp.<snake_case> namespace with no mixed casing or conventions. Most use a verb_noun form (run_vspaero, set_parameters, batch_submit), but several are bare single words (preview, preflight, health, query, inspect, sweep, modify), a minor deviation from a fully uniform pattern.

    Tool Count4/5

    16 tools is on the heavier side for the scope, but each earns its place: a batch lifecycle legitimately requires submit/status/cancel/resume/export, and health/inspect/query/preview cover distinct inspection levels. Slightly over but well-justified rather than redundant.

    Completeness4/5

    The surface covers the full lifecycle: health readiness, XML/native inspection, model creation/modification, parameter edits, geometry preflight, preview export, single/sequential/batch solving, results reading, and batch export. Minor gaps like batch or model deletion are absent but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources