Skip to main content
Glama
0xFFD

openfoam-mcp

by 0xFFD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to openfoam-mcp

No user-submitted related servers found.

    Related Servers

    • openfoam-mcp

      kimlnw
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns an AI assistant into an OpenFOAM setup and debugging co-pilot, enabling case scaffolding, dictionary edits, mesh sizing, turbulence calculations, and solver log analysis through natural language.
      MIT

    • 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
    • NovaSolver Studio MCP Server by novasolver

      NovaSolver Studio MCP Serverofficial

      novasolver
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to set up, run and verify engineering simulations through typed tools — creating or importing cases, setting boundary conditions, running solvers, checking convergence, verifying results against references, and rendering output, with edits appearing live in the GUI. It exposes no shell or code-execution tool.
      GPL 3.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
    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.4/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions (case creation, file I/O, dictionary editing, job control, post-processing). However, some overlap exists: read_file also reads dictionaries alongside get_dict, and job_status, solver_progress, and read_log all partially cover log/monitoring use cases. Descriptions help differentiate, but these boundaries are not perfectly crisp.

    Naming Consistency4/5

    All names use snake_case, and the dominant pattern is verb_noun (e.g., create_case, list_files, read_log). Deviations are mostly conventional noun phrases for info/status tools (foam_info, job_status) and two bare verbs (run, render), which are readable but not perfectly uniform.

    Tool Count3/5

    At 25 tools, the surface feels heavy for the domain, sitting at the upper end of the rubric's borderline range. While most tools are individually justified for a complex CFD workflow, some consolidation (e.g., monitoring/log tools, file/dict operations) could reduce the count without losing capability.

    Completeness4/5

    The surface covers the main OpenFOAM lifecycle: case setup, file/dictionary editing, running solvers, monitoring, mesh checking, post-processing, and rendering. Minor gaps exist, such as file-level delete/move/rename operations and dedicated mesh-generation tools (though run can invoke them), but these are workable for an agent.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources