hexpress-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | No | Path to the hexpress-mcp source directory (e.g., D:\path\to\hexpress-mcp\src). | |
| PYTHONUTF8 | No | Set to 1 to enable Python UTF-8 mode for non-ASCII paths. | |
| HEXPRESS_DIR | No | Optional path to the HEXPRESS installation directory. If omitted, the server auto-discovers C:\NUMECA_SOFTWARE\hexpress*\bin64\hexpressx86_64.exe and caches the path to %APPDATA%\hexpress-mcp\config.json. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusA | Probe the environment: HEXPRESS install paths, executables, license server state, whether the GUI is running, and platform notes. Call first. |
| generate_confA | Generate a HEXPRESS batch .conf file (without running it). input_files: geometry/mesh inputs (STL, .spb, .CATPart, .igs ...), absolute paths recommended. output_mesh: output file name, e.g. resultMesh.msh (FNMB mesh) or .spb.gz. base_h: base cell size for the octree mesher. refinements: {selection_name: [initial_level, min_level]} — LOCALREFINEMENTDEFINITION. boundary_conditions: {selection_name: bc_type} — BCDEFINITION (e.g. SOL, INL, OUT, SYM). num_boundary_layers: viscous layer count (NUMBNDLAYERS). s2v_mesh: surface-to-volume (tet-dominant) mode instead of octree hybrid. Returns the written path and the full conf content. |
| run_meshA | Run hexpresshybridx86_64.exe on a .conf file (generate a mesh in batch). conf_file: path returned by generate_conf (or any HEXPRESS-exported conf). np: number of MPI processes (>1 adds -ompi -np N). timeout: seconds before the run is killed (default 1 h; big meshes need more). Returns returncode, elapsed time, output file info and the log tail. |
| run_scriptA | Run a Python 2 script inside headless HEXPRESS (-batch -script). The script executes with the embedded HXP API preloaded (HXP.open_project,
HXP.generate_initial_mesh, HXP.insert_viscous_layers, ... — see
_python/_igg/HXP.py in the install), wrapped so that its stdout (which
HEXPRESS batch mode otherwise swallows) is captured, and a
SCRIPT_RETURN_VALUE line — printed as |
| convert_fileB | Convert between mesh/geometry formats (hexpressfileconvertx86_64.exe). e.g. .spb -> .msh, .spb.gz -> .cgns ... Formats are inferred from the extensions. Returns returncode and the log tail. |
| convert_cadA | Re-export a Parasolid CAD file through the HEXPRESS GUI kernel. hexpresshybridx86_64.exe (batch mesher) can segfault (0xC0000005) reading newer Parasolid transmits that hexpressx86_64.exe imports fine — passing the file through this converter (import + export) produces a byte-level V32-era transmit the batch mesher digests. Also useful to bake/validate any Parasolid .x_t/.x_b before meshing. Output defaults to _v32.X_T next to the input. Returns the exported path. |
| inspect_geometryA | Report the selection names a geometry file will produce for BCDEFINITION / LOCALREFINEMENTDEFINITION in a batch conf. For .stl: reads the solid names directly (hexpresshybridx86_64 groups triangles by STL solid name — import_mode 2, the default). Empty-string names mean a binary STL (no names stored) — use feature grouping (import_mode 1) there and discover TMP-style names from the mesh log. For .spb/.igg project files the names live inside the project; open it in the GUI once or query via run_script. Non-STL inputs raise an error. |
| launch_guiC | Start the interactive HEXPRESS GUI (hexpressx86_64.exe), detached. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a fairly distinct role, but boundaries blur in a couple of places: convert_file and convert_cad both perform format conversion, and run_script is a general escape hatch that could overlap with generate_conf/run_mesh for a determined agent. Descriptions do clarify the differences, so misselection risk is low but not zero.
All eight names follow a strict verb_noun snake_case pattern (get_status, generate_conf, run_mesh, run_script, convert_file, convert_cad, inspect_geometry, launch_gui). No style mixing or vague single-word names.
Eight tools is well within the healthy 3-15 range for a domain-specific meshing server. Each tool maps to a distinct stage of the workflow (probe, generate, run, script, convert, inspect, launch), so all earn their place.
The surface covers the full meshing lifecycle from environment probing through conf generation, execution, conversion, and geometry inspection. Minor gaps exist: there is no tool to cancel/terminate an in-flight job or to inspect mesh quality/results post-run, which agents may need to work around.