FEP Agent Hub

Run the three MCP servers as independent stages joined by manifests, semantic IDs, native solver artifacts, and explicit physics gates. Preserve auditability over convenience.

Establish the run contract

1. Locate the FEP Agent Hub repository and read its AGENTS.md, root README, relevant prompt, and relevant report before changing a workflow.
2. Resolve native executables through OPEN_CAE_CONFIG, environment variables, or configs/open-cae.local.toml. Treat public paths as placeholders.
3. Choose a unique project name beneath the configured workspace. Keep FCStd, STEP, mesh, SIF, logs, VTU/PVD, images, tables, and evidence inside that project.
4. Probe all three MCP environments before modeling. Stop if a required native executable or server is unavailable.
5. Never expose arbitrary shell, Python, executable, macro, MATC, or raw SIF input. Use only fixed runners, structured parameters, and allowlisted analysis profiles.

Select a verified profile

Read references/case-catalog.md when selecting a profile, copying benchmark parameters, or deciding whether the request exceeds verified capability.

Use a listed profile only for the physics and dimensionality it declares. Add a new profile, deterministic benchmark, tests, and gates before claiming a new class of analysis is supported.

Orchestrate the native chain