Skip to main content
Glama
vegetableno1

dualsphysics-mcp

by vegetableno1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to dualsphysics-mcp

No user-submitted related servers found.

    Related Servers

    • Foam-Agent

      KasperHonore
      A
      license
      Not graded
      quality
      A
      maintenance
      Automates OpenFOAM CFD simulations via MCP, enabling AI agents to mesh, run, and post-process cases from natural language prompts without any API keys.
      MIT
    • Ansys CFX-MCP by ansys

      Ansys CFX-MCPofficial

      ansys
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI assistants to interact with Ansys CFX through PyCFX, supporting natural-language-assisted CFX-Pre, CFX Solver, and CFD-Post workflows for setup, execution, and postprocessing.
      7
      344 PyPI
      Apache 2.0

    • vCFD

      gpu7
      A
      license
      A
      quality
      A
      maintenance
      Voice-driven CFD MCP server that enables natural language setup, execution, and analysis of OpenFOAM simulations, with results exportable to ParaView.
      16
      MIT

    • FEP Agent Hub

      S2mon123
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables evidence-first CAE automation on Windows through local MCP servers for FreeCAD, Elmer FEM, and ParaView, supporting validated workflows from CAD to simulation and post-processing with a shared safety and evidence runtime.
      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.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct stage of the DualSPHysics workflow (environment check, case generation, execution, polling, conversion, measurement, validation). No overlap in purpose; even validate_dambreak and measure_tool are clearly separated (measure produces CSV, validate analyzes it).

    Naming Consistency4/5

    Mostly consistent snake_case with verb_noun pattern (validate_dambreak, check_environment, run_case, measure_tool). Minor deviations: partvtk and gencase lack underscores, and job_status is noun_verb rather than verb_noun, but overall the pattern is predictable and readable.

    Tool Count5/5

    Seven tools cover the entire simulation lifecycle for a focused domain (dam-break validation). The count is well-scoped and each tool clearly earns its place; no bloat or deficiency.

    Completeness4/5

    The core workflow is covered end-to-end: generate case, run solver, monitor status, measure quantities, validate against experiment, and visualize results. Minor gaps include lack of job restart/cancel and no handling of wave generation, but these are acknowledged limitations rather than missing essential steps for the stated dam-break use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources