OpenFOAM MCP servers and AI agent skills

How AI connects to OpenFOAM

An MCP server or skill can only do what OpenFOAM lets programs do. OpenFOAM exposes 2 automation interfaces:

• Case dictionaries (0/, constant/, system/) (Input files): An OpenFOAM case is a folder of plain-text dictionaries: initial and boundary fields in 0/, physical properties in constant/, and controlDict, fvSchemes and fvSolution in system/. That makes every case scriptable without an API, and it is why file-only servers can edit boundary conditions or solver settings without OpenFOAM installed. The foamDictionary utility reads and writes single entries safely, and foamToC lists the available boundary conditions, models and solvers. Documentation
• Utilities and solvers from the shell (Command line): Meshing (blockMesh, snappyHexMesh, checkMesh), decomposition and solving are separate executables run in a sourced OpenFOAM environment, often through an Allrun script. Releases from openfoam.org since version 11 use foamRun with modular solvers, while openfoam.com releases such as v2412 keep named solvers like simpleFoam, so a server built for one line may call commands the other doesn't have. Documentation

What Open source offers

Neither openfoam.org nor openfoam.com lists an MCP server, AI assistant or agent among its downloads or documentation as of this check. All the AI integrations here are community or academic projects; Foam-Agent, from a university research group, publishes benchmark results on its FoamBench task set, including runs with Claude models.

Checked 4 Nov 2026. Sources: openfoam.org, openfoam.com, Foam-Agent README (reported benchmark results)

What you can do with OpenFOAM and AI

• Clone a tutorial such as pitzDaily or motorBike, edit its dictionaries, mesh it with blockMesh or snappyHexMesh and run it in parallel, with the agent watching residuals and Courant number.
• Turn a plain-language description into a complete case, run it and let the agent repair the files when the solver stops with a FOAM FATAL ERROR.
• Compare a lid-driven cavity or backward-facing step against Ghia or Armaly reference data, with a REPORT.md recording each decision.
• Edit boundary conditions, transport properties or radiation settings in an existing case without launching OpenFOAM.
• Get slices, streamlines or force-coefficient plots back as images from a headless ParaView.

Taken from the listings' own documentation. Check each listing for exactly what it supports.

Installing

The listings here document setup for Claude Code, Claude Desktop, Cline, Codex, Cursor, Gemini CLI, GitHub Copilot (VS Code and CLI), GitHub Copilot CLI, Kilo, OpenCode, VS Code, Windsurf and opencode. Install steps, copied from each project's own documentation, are on each listing's page. Most OpenFOAM integrations run on your own computer next to OpenFOAM, so you need OpenFOAM installed and licensed on the same machine unless the listing says otherwise.