avl-mcp
Related Servers
Alternatives to avl-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceProvides aerodynamic analysis tools through MCP, enabling geometry generation, meshing, CFD solving, and visualization for 2D airfoils.7-
- AlicenseAqualityBmaintenanceEnables MCP clients to build, inspect, validate, render, and simulate Vensim PLE system dynamics models from .mdl files, including parameter overrides, sweeps, and CSV result export.17MIT
- AlicenseBqualityBmaintenanceEnables any MCP client to plan and run verifiable analysis of engine hot-fire and bench test data through tools that open runs, segment phases, check sensor health, redlines, valve response and oscillations, compare simulations, verify every reported number against an evidence ledger, and write HTML reports. All findings stay traceable and reproducible from deterministic tool calls rather than raw samples.538 PyPIMIT
- AlicenseAqualityBmaintenanceMaintained fork of Three-Little-Birds/openvsp-mcp, adding OpenVSP geometry inspection, typed parameter editing, SVG/STL previews, validated VSPAERO analysis, and durable parallel batches with progress, cancellation, resume, and CSV/JSON export. Independently maintained by rhyne1012; not an official OpenVSP or NASA project.18MIT
- AlicenseBqualityDmaintenanceEnables aerodynamic analysis through XFOIL polar computations. Provides typed models and tools to run airfoil performance analyses from agents or automation workflows.1MIT
- 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
TDQS
Scored across 14 tools
Most tools have clearly distinct roles: single-case run, multi-case sweep, detached submit, and job control/status/results are readily separable. The main ambiguity is within the trim family (prepare_trim, trim, trim_physical), though their descriptions clarify whether AVL is executed and what inputs are required.
All names use lower snake_case under the avl. namespace, which is consistent at the lexical level. However, the set mixes imperative verbs (run, sweep, submit, inspect) with noun-like resource names (status, results, health) and compound descriptive forms (mesh_sensitivity, trim_physical), so it is readable but not a predictable verb_noun convention.
Fourteen tools is well within the appropriate range for a complex AVL analysis server. Each major phase—inspection, validation, execution, background job control, and result retrieval—has a dedicated tool without obvious filler.
The surface covers the core AVL lifecycle: inspect/validate/health, trim preparation, run/sweep/submit, status/cancel/resume, and results retrieval. Minor gaps such as a job-list operation or explicit geometry/setup management are not central to the apparent analysis scope, but there is no obvious dead end.