Skip to content

Cai-aa/CAE-Agent-Hub

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

21 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CAE Agent Hub

Language: English | 中文

CAE Agent Hub is a collection of MCP servers, reusable agent skills, solver automation scripts, and browser result viewers for mainstream engineering simulation software. The goal is to let AI coding clients such as Codex, Cursor, Claude Code, or Claude Desktop work with real CAE tools instead of only generating offline examples.

The current repository includes:

  • MCP servers for Abaqus/CAE, ANSYS Fluent, ANSYS Workbench Mechanical, and Ansys Electronics Desktop / HFSS.
  • Abaqus-focused finite element skills organized by workflow stage.
  • The original Text to CAE browser viewer for inspecting exported result_mesh.json simulation results.
  • Example workflows and templates that keep solver binaries, licenses, private paths, and generated results out of source control.

Repository

https://github.com/Cai-aa/CAE-Agent-Hub

The old text-to-cae name is kept in some folder names for compatibility with existing viewer cases.

Architecture

AI client
  -> MCP server or skill instruction
  -> live CAE application or solver script
  -> native solver results
  -> exported lightweight viewer data
  -> browser inspection or report workflow

This repository separates responsibilities:

  • MCP servers provide live tool access to installed CAE applications.
  • Skills provide reusable modeling, setup, solving, postprocessing, and validation instructions.
  • CAE applications perform the real solve.
  • Viewer modules inspect exported result data without requiring the solver to be open.

MCP Index

MCP Status Purpose Main entry points Trigger keywords
Abaqus MCP Active Connect MCP clients to a live Abaqus/CAE session through a local TCP bridge; run Python in the Abaqus kernel, inspect models, submit jobs, monitor status, inspect ODB files, and capture viewport images. mcp_server.py, abaqus_mcp_plugin.py, abaqus_plugins/mcp_control/ Abaqus MCP, Abaqus/CAE, ODB, viewport, submit job, live Abaqus
ANSYS Fluent MCP Active Detect Fluent, launch batch journals, track jobs/logs, and optionally manage live PyFluent sessions for Scheme, TUI, and Python probes. server.py, tools/fluent_bridge.py, tools/pyfluent_session.py Fluent, PyFluent, journal, TUI, CFD, Scheme
ANSYS Workbench MCP Active Control Workbench and Mechanical through Python helpers plus an ACT bridge, with file-queue and socket-timer communication modes. server.py, tools/, workbench_plugin/ Workbench, Mechanical, ACT, LS-DYNA, socket timer
Ansys AEDT MCP Active Connect MCP clients to Ansys Electronics Desktop / HFSS through a raw TCP JSON bridge; inspect projects, create HFSS designs, save projects, and run small AEDT Python snippets. mcp_server.py, aedt_mcp_bridge.py, scripts/install_aedt_toolkit_button.ps1 AEDT, HFSS, Electronics Desktop, antenna, S-parameters

Adding a new MCP? Follow this pattern: keep reusable source, examples, tests, and bilingual README files; exclude virtual environments, solver results, private paths, licenses, and generated project data.

Skill Index

Skill Status Purpose Trigger keywords
abaqus Active Master router for Abaqus FEA scripting and analysis workflows. Abaqus, FEA, finite element, simulation, route skills
abaqus-geometry Active Create parts, sketches, extrusions, assemblies, and import CAD. geometry, part, sketch, extrude, STEP, IGES
abaqus-material Active Define materials, sections, density, elasticity, plasticity, and common engineering properties. material, steel, aluminum, Young's modulus, plastic
abaqus-mesh Active Generate finite element meshes and choose element types. mesh, elements, nodes, C3D8R, refine
abaqus-interaction Active Define contact, friction, tie constraints, connectors, and bonded surfaces. contact, friction, tie, touching parts, bonded
abaqus-amplitude Active Define time-varying amplitudes for ramp, pulse, cyclic, or transient loads. amplitude, ramp, pulse, cyclic, time-varying
abaqus-bc Active Define boundary conditions such as fixed, pinned, clamped, displacement, and symmetry constraints. fixed, clamped, pinned, support, constraint
abaqus-docs Active Download and manage abqpy / Abaqus API documentation. Abaqus docs, API reference, abqpy
abaqus-field Active Define initial conditions and predefined fields such as initial temperature or residual stress. initial condition, predefined field, residual stress
abaqus-load Active Apply concentrated forces, pressures, gravity, and distributed loads. force, pressure, gravity, load
abaqus-output Active Configure field and history output requests. output request, field output, history output
abaqus-step Active Define analysis steps, procedures, increments, time periods, and nonlinear geometry settings. step, static step, dynamic step, frequency, nlgeom
abaqus-static-analysis Active Complete static structural workflow for stress, displacement, reactions, strength, and stiffness. static, stress, displacement, strength, reaction force
abaqus-modal-analysis Active Extract natural frequencies and mode shapes for vibration and resonance checks. modal, frequency, vibration, resonance, mode shape
abaqus-dynamic-analysis Active Complete dynamic workflow for impact, crash, drop test, transient, explicit, or implicit dynamics. impact, crash, drop test, transient, explicit
abaqus-thermal-analysis Active Heat transfer workflow for steady-state or transient temperature distribution. thermal, heat transfer, conduction, convection
abaqus-coupled-analysis Active Coupled thermomechanical workflow for thermal stress and temperature-driven deformation. thermal stress, expansion, temperature deformation
abaqus-contact-analysis Active Multi-body contact workflow for friction, press fit, bolts, and assemblies. contact analysis, friction, press fit, bolt
abaqus-fatigue-analysis Active Fatigue and durability workflow for cycles, damage accumulation, and life prediction. fatigue, durability, cycles, life prediction
abaqus-job Active Create, submit, monitor, and manage Abaqus jobs and input files. run analysis, submit job, input file, execute
abaqus-export Active Export Abaqus geometry and results to STL, STEP, CSV, INP, or external formats. export, STL, STEP, CSV, INP
abaqus-odb Active Read ODB results and extract stress, displacement, reaction force, and result summaries. ODB, maximum stress, displacement, reaction force
abaqus-optimization Active Configure Tosca optimization responses, objectives, constraints, and SIMP-style settings. optimization, objective, constraint, Tosca
abaqus-shape-optimization Active Optimize fillet/notch/surface shape to reduce peak stress without topology removal. shape optimization, fillet, notch, stress concentration
abaqus-topology-optimization Active Topology optimization workflow for reducing mass while preserving stiffness. topology optimization, weight reduction, stiffness
fea-structural Reference General structural FEA guidance across static, dynamic, nonlinear, and validation domains. structural FEA, nonlinear, validation
fenics-fem Reference FEniCS/dolfinx finite element reference for weak forms, gmsh meshes, PDEs, and ParaView export. FEniCS, dolfinx, PDE, weak form, gmsh

Adding a new skill? Keep the complete skill directory together with SKILL.md, metadata.json when available, upstream attribution, references, assets, and any scripts needed by the workflow.

Installation

Clone

git clone https://github.com/Cai-aa/CAE-Agent-Hub.git
Set-Location .\CAE-Agent-Hub

If you cloned the repository before the rename, the old text-to-cae remote may still work through GitHub redirects. Updating the remote URL is clearer:

git remote set-url origin https://github.com/Cai-aa/CAE-Agent-Hub.git

Use an MCP server

Each MCP folder has its own README and environment template. The common local pattern is:

Set-Location ".\MCP\<vendor>\<server folder>"
py -m venv .venv
.\.venv\Scripts\python.exe -m pip install -U pip
.\.venv\Scripts\python.exe -m pip install -e .

Then register the server with your MCP-capable client using the example config in that folder.

Use skills

Skills are instruction modules, not solver binaries. Copy the complete skill directory into your agent's skill directory or attach the relevant SKILL.md as project context.

Codex example:

New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.codex\skills" | Out-Null
Copy-Item -Recurse -Force ".\Skill\abaqus\analysis\abaqus-static-analysis" "$env:USERPROFILE\.codex\skills\abaqus-static-analysis"

Suggested prompt:

Use the abaqus-static-analysis, abaqus-mesh, abaqus-job, and abaqus-odb skills. Build a complete Abaqus static-analysis workflow, run it if the Abaqus MCP or local Abaqus CLI is available, and report the exact files and commands used.

Text to CAE Viewer

The viewer is still included as the browser result-inspection layer. It can display cases that contain result_mesh.json even when the solver is not installed.

Set-Location .\viewer
npm.cmd install
npm.cmd run dev

Open the Vite URL, usually:

http://127.0.0.1:4178/

Example cases:

http://127.0.0.1:4178/?case=cantilever
http://127.0.0.1:4178/?case=hole-plate
http://127.0.0.1:4178/?case=hole-plate-modal
http://127.0.0.1:4178/?case=sphere-impact
http://127.0.0.1:4178/?case=milling-3d
http://127.0.0.1:4178/?case=gear-mesh
http://127.0.0.1:4178/?case=bullet-plate

Repository Layout

CAE-Agent-Hub/
  MCP/
    Abaqus/
    Ansys/
      AEDT MCP/
      Fluent MCP/
      Workbench MCP/
  Skill/
    abaqus/
      core/
      modeling/
      setup/
      analysis/
      execution/
      postprocessing/
      optimization/
      reference/
  models/
  viewer/

Source Control Policy

The repository should include reusable source, documentation, tests, examples, templates, and skill instructions.

It should not include:

  • CAE software binaries or licenses.
  • Private machine paths or credentials.
  • Virtual environments and package caches.
  • Generated solver outputs such as ODB, case/data, AEDT results, Workbench projects, logs, and screenshots.
  • Large local result artifacts that can be regenerated.

Build

Build the frontend viewer:

Set-Location .\viewer
npm.cmd run build

Roadmap

The hub is designed to grow toward more mainstream simulation ecosystems:

  • More solver-specific MCP servers.
  • More productized skill packs for repeatable modeling and validation workflows.
  • Shared result export formats for viewer and report generation.
  • Safer install prompts and verification scripts for each CAE application.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors