Skip to main content
Glama
rhyne1012

avl-mcp

by rhyne1012
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to avl-mcp

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

    • su2-mcp

      cmudrc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with SU2 CFD solver for session lifecycle management, config editing, solver execution, and results inspection, with optional CPACS integration for aircraft analysis.
      4
      MIT

    • pyNastran MCP Server

      Shaoqigit
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to interact with Nastran FEA models by reading, writing, and analyzing BDF and OP2 files. It provides tools for mesh quality assessment, geometric analysis, and automated report generation for structural engineering workflows.
      3
      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/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: environment health, input inspection, validation, single run, sweep, async submit, status, cancel, resume, and results retrieval. Overlapping concerns like dependencies appear in multiple tools but are explicitly separated by context (environment vs. input file). There is little risk of an agent selecting the wrong tool.

    Naming Consistency4/5

    Tool names are uniformly lowercase single-word commands, which is easy to follow. Most are imperative verbs (inspect, validate, run, submit, cancel, resume), but health, status, and results are noun-style names that deviate slightly from a strict verb pattern.

    Tool Count5/5

    Ten tools cover the AVL workflow without redundancy or bloat. The count is well within the ideal range and each tool contributes a necessary part of the simulation lifecycle.

    Completeness5/5

    The toolset covers the full workflow: environment checks, inspection, validation, synchronous single/multi-case execution, asynchronous submission, job control, and result retrieval. There are no obvious dead ends, and background jobs can be managed and resumed cleanly.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources