OpenVSP MCP (Maintained Fork)
Related Servers
Alternatives to OpenVSP MCP (Maintained Fork)
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables automated geometry editing and aerodynamic analysis using OpenVSP and VSPAero through natural language. Provides tools to modify aircraft geometry parameters and run computational fluid dynamics simulations programmatically.37MIT
- FlicenseAqualityDmaintenanceProvides aerodynamic analysis tools through MCP, enabling geometry generation, meshing, CFD solving, and visualization for 2D airfoils.7-
- AlicenseBqualityBmaintenanceProvides MCP tools for CPACS-oriented TiGL workflows, enabling lifecycle management, inspection, export, and parameter manipulation of aircraft geometry models without native geometry runtimes.113MIT
- AlicenseAqualityAmaintenanceEnables running reproducible AVL 3.52 aerodynamic analyses through MCP, with input validation, isolated execution, sweeps, background jobs, and structured results including solver files.14GPL 2.0
- FlicenseAqualityBmaintenanceCAD-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-
- AlicenseNot gradedqualityBmaintenanceAn 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
Scored across 18 tools
The tools have mostly distinct purposes, and descriptions explicitly cross-reference alternatives such as query vs inspect vs preflight vs health and run_vspaero vs sweep vs batch_submit. However, the set has several closely related introspection and execution tools, so an agent may still need to read descriptions carefully to choose correctly.
All names use snake_case with a consistent openvsp. prefix, and most use clear verb_noun or batch_* patterns. A few tools are noun-like or bare actions (query, health, inspect, preview, preflight), which is a minor deviation from a strict verb_noun convention.
The 18 tools cover a broad but real domain: model creation/editing, inspection, geometry export, VSPAERO execution, and batch lifecycle management. The count is slightly above the typical 3-15 range, but most tools appear to earn their place rather than being redundant.
The surface covers the main OpenVSP/VSPAERO lifecycle: creation, inspection, modification, preflight, single/sweep/batch solving, result reading, and batch control. Minor gaps remain around model duplication/deletion or operation discovery, but core workflows are well supported.