sim-cli
Reads COMSOL, Abaqus, Fluent and other CAE files into structured JSON for agents, without launching the solver.
- 247 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The base `scan` command only reads files, while solver packages drive scripts and live sessions on your machine.
- Some packages are installed straight from the repository through Git instead of PyPI.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/sim-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The base `scan` command only reads files, while solver packages drive scripts and live sessions on your machine.
- Some packages are installed straight from the repository through Git instead of PyPI.
This is third-party code. Review the repository files before installing.
What it does
The `sim` command parses finished engineering-simulation files and gives an agent compact JSON: model title, node and element counts, materials, steps, boundary conditions and loads. A single `sim --json scan ./historical-cases` call handles a whole folder with no solver, license server or vendor SDK. Supported are COMSOL (`.mph`), Abaqus (`.inp`), Fluent, Ansys Electronics Desktop and Mechanical, Icepak, FloTHERM, Simulink and MATLAB data. Output is bounded so a large scan fits in the agent's context, and absolute paths are hidden by default. By the authors' benchmark the parser is four to twenty times faster than an equivalent Python script. When the agent must also detect an installed solver, lint scripts or drive a live session, separate `sim-plugin-<solver>` packages are installed, each with its own skill.
Who it is for. Simulation engineers and CAE teams who want to ask an agent about accumulated COMSOL, Abaqus or Fluent models.
Good fit when
- An archive holds hundreds of old simulations and the agent must find models with a given material or load type.
- A `.mph` or `.cas.h5` file arrived without documentation and must be understood quickly.
- A solver license is not at hand but the model structure has to be read.
- The agent prepares a report on a set of Abaqus models and compares steps and boundary conditions.
- An installed COMSOL or Fluent should be connected to the agent and scripts checked before running.
Not a fit when
- A simulation must be run or field results obtained: the base `scan` command reads only the model description.
- The file format is not on the supported list: the parser recognises the listed extensions.
- The workflow is already built on the solver API and reading files is not needed.
Example request
Scan the ./cases folder and list the Abaqus models with the STEEL material, showing steps and load keywords.Limitations
The base `sim-cli-core` package reads files and computes nothing: solver detection and the `sim check`, `sim lint`, `sim run` and `sim connect` commands need separate `sim-plugin-<solver>` packages. Some packages, such as FloTHERM, STAR-CCM+, HyperMesh and SpaceClaim, are not yet on PyPI and are installed straight from the project repository through Git. The solvers themselves are not bundled, so their licenses and installation stay on your side. The full parser result is printed only with `--full` and suits small sets of files. Details for each format are in `docs/simparse.md`.
How to disable. Drop the dependency with `uv remove sim-cli-core` and remove installed `sim-plugin-<solver>` packages the same way. Delete skills copied into `.agents/skills` by hand.
FAQ
How do I install sim-cli for Claude Code?
In a uv project run `uv add sim-cli-core` (if there is no project yet, run `uv init` first). Then run commands such as `uv run sim --json scan ./historical-cases`.
Is an installed solver needed?
No, the `scan` command needs no solver, license server or vendor SDK. A solver is required only when working through `sim-plugin-<solver>` packages.
Which file formats does the parser read?
COMSOL `.mph`, Abaqus `.inp` and `.inc`, Fluent `.cas.h5` and `.msh.h5`, Ansys `.aedt`, `.mechdb`, Icepak `.tzr`, FloTHERM `.pack`, `.xml`, `.floxml`, Simulink `.slx`, `.mdl` and MATLAB `.mat`. The `--format` flag forces a format.
How do I give the agent solver skills?
Install a package such as `uv add sim-cli-core sim-plugin-comsol` and run `uv run sim plugin sync-skills --target .agents/skills --copy`. Then verify with `uv run sim check comsol`.
What does the agent see in the response?
A stable JSON envelope with `ok`, `engine`, `request` and a summary per file, with errors carrying codes from a closed list. `sim --json describe` prints the full command set.
Discussion
No questions or reviews yet.
Related
CLI toolsThe official MathWorks kit that gives an agent MCP tools and knowledge to work with Simulink models
An MCP server with a library of typed math operations: the agent finds one, runs it and passes the result on to the next
jc converts command output, files and strings into JSON with dedicated parsers for use in scripts and downstream tools.
A 2D hydraulic modeling package with an MCP server and skills: an agent opens an SRH-2D or HEC-RAS project and runs simulations.
A skill and Python package for hyperparameter tuning: the agent reads the code, proposes the next set of values, and your own run measures the result
An MCP server with 35 tools for EnergyPlus building energy models: loading IDF files, editing parameters, simulation and plots.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| sim-cli (this card) | no | 247 | |
| MATLAB Agentic Toolkit | no | 1,269 | MathWorks' official kit with an MCP server for running MATLAB code; here reading COMSOL, Abaqus and Fluent files without launching |
| Simulink Agentic Toolkit | no | 1,324 | official tools for working with Simulink models; here Simulink is one of the supported formats |
README in short
The project is built around an agent-readability contract: standard flags, a stable response envelope and self-description through `sim describe`. Commands never ask for keyboard input, and the Apache-2.0 license covers the parser and the solver packages in the repository.