Skip to main content
Glama
hexpress-mcp

hexpress-mcp

by GaillumXc

Related Servers

Alternatives to hexpress-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      4
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      25
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Automates OpenFOAM CFD simulations via MCP, enabling AI agents to mesh, run, and post-process cases from natural language prompts without any API keys.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      5
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Turns 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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues