Skip to main content
Glama
Three-Little-Birds

Flappy MCP Server

by Three-Little-Birds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Flappy MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      10
      GPL 2.0

    • OpenVSP MCP (Maintained Fork)

      rhyne1012
      A
      license
      A
      quality
      A
      maintenance
      Maintained 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.
      16
      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
    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

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'flappy.simulate' has a clearly defined and distinct purpose for running a Flappy dynamics simulator.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'flappy.simulate' follows a clear verb_noun pattern with no deviations or mixing of conventions.

    Tool Count2/5

    A single tool is too few for the apparent scope of a Flappy dynamics simulator server, which typically involves complex mission profiles, morphology, and control schedules. This minimal toolset feels thin and likely incomplete for the domain.

    Completeness2/5

    The tool surface is severely incomplete for a dynamics simulator domain. There are obvious gaps such as tools for configuring scenarios, retrieving past simulations, managing mission profiles, or analyzing results, which will cause agent failures in typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources