FEP Agent Hub
MCP serverCommunity
Three local MCP servers for a FreeCAD to Elmer FEM to ParaView chain, with workspace limits and physics checks on every result. By S2mon123.
5 starsUpdated 3 months agoGitHub data from 5 Nov 2026
At a glance
- Type
- MCP server
- How it connects
- Drives a running copy of the tool
- Access
- Can modify models
- Tool versions
- unknown (paths to FreeCAD, Gmsh, Elmer and ParaView executables are set in a local config)
- Operating systems
- Windows
- Needs a ParaView licence
- No
- Transport
- Local (stdio)
- AI clients documented
- Codex
- Licence
- MIT
- Language
- Python
What it can do
- FreeCAD server (15 tools) builds parametric CAD and hands off STEP; Elmer server (17 tools) meshes with Gmsh, converts with ElmerGrid, writes SIF files and solves.
- ParaView server (17 tools) runs persistent headless post-processing and exports images, CSV and PVSM state.
- Requires process, log, artifact, finite-value and physics gates before a step counts as passed, and returns BLOCKED for unsupported requests instead of fabricating output.
- Ships a Codex skill that enforces the FreeCAD, Elmer, ParaView order across six tested profiles (heat, transformer, beam, channel flow, eddy current).
Limitations
- Windows-oriented and registered with Codex by its scripts; other clients need manual setup.
- No arbitrary shell or Python tools; work is limited to the tested profiles and tools.
- Use a short ASCII-only workspace path, as some native solvers fail on Unicode paths.
Install
.\scripts\install.ps1
$env:OPEN_CAE_CONFIG = "$PWD\configs\open-cae.local.toml"
.\.venv\Scripts\python.exe .\scripts\doctor.py
.\scripts\register-codex.ps1MCP servers and skills run code on your computer. Review the source before installing.
AI-generated models, drawings and results must be checked by a qualified engineer before use.