hexpress-mcp
Related Servers
Alternatives to hexpress-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to automate preprocessing workflows, including geometry queries, surface and volume meshing, mesh quality checks, entity/property management, script execution, and task tracking through a native control panel.4MIT
- AlicenseBqualityBmaintenanceEnables AI agents to drive OpenFOAM end to end: cloning tutorials or custom cases, editing dictionaries, meshing and running solvers in the background, tracking convergence and job status, and analyzing results. It also renders flow images — slices, patches, streamlines, iso-surfaces and residual or force plots — back to the agent.251MIT
- AlicenseNot gradedqualityAmaintenanceAutomates OpenFOAM CFD simulations via MCP, enabling AI agents to mesh, run, and post-process cases from natural language prompts without any API keys.MIT
- AlicenseAqualityCmaintenanceEnables AI agents on Windows to control Altair Inspire through its headless batch mode and Python API, including running scripts, inspecting models, summarizing .h3d results, and exporting OptiStruct decks without opening or touching the GUI.5MIT
- FlicenseNot gradedqualityCmaintenanceEnables an AI assistant to drive Abaqus/CAE through file IPC—sending Python commands, querying model info, submiting jobs, and capturing viewport screenshots—so finite element models can be built and solved without manual GUI interaction.2-
- AlicenseNot gradedqualityCmaintenanceTurns an AI assistant into an OpenFOAM setup and debugging co-pilot, enabling case scaffolding, dictionary edits, mesh sizing, turbulence calculations, and solver log analysis through natural language.MIT
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.