Skip to main content
Glama
Ultron-1-7

mikezero-mcp

by Ultron-1-7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mikezero-mcp

No user-submitted related servers found.

    Related Servers

    • mike-plus

      Zhonghao1995
      A
      license
      A
      quality
      B
      maintenance
      A headless, natural-language-driven automated modelling workflow for MIKE+, enabling users to inspect models, change parameters, run simulations, and analyze results without the MIKE+ GUI.
      10
      7
      MIT

    • autocad-mcp

      ks40-academy
      A
      license
      A
      quality
      D
      maintenance
      Enables automation of AutoCAD LT and headless DXF creation through two backends (File IPC for Windows AutoCAD LT and ezdxf for cross-platform) with tools for drawing, entity, layer, block, annotation, PID, view, and system operations.
      8
      7
      MIT

    • su2-mcp

      cmudrc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with SU2 CFD solver for session lifecycle management, config editing, solver execution, and results inspection, with optional CPACS integration for aircraft analysis.
      4
      MIT

    • Codex MCP Abaqus

      Zhangyoupeng1996
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables to interact with Abaqus FEA software through an MCP bridge, supporting connection checks, script execution, model queries, job submission, and simulation automation.
      3
      -

    • hecras-mcp

      danielmiranda2017-tech
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to drive HEC-RAS headless — inspecting projects, validating and executing 1D steady, 1D unsteady and 2D plans, and reading hydraulic results from HDF5 files. It also supports limited model modification, such as setting steady discharges, all without the Windows desktop application or a programmatic API.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct phase: environment detection, engine mapping, file scanning, setup parsing, job execution, progress tracking, batch runs, toolbox runs, job management, and result analysis. Even the closely related mz_progress and mz_job_status are clearly separated by their data sources (progress file vs process/log).

    Naming Consistency4/5

    All tools share the mz_ prefix and group logically (mz_job_* for lifecycle, mz_dfs_* for results), making the pattern predictable. Minor inconsistency exists between noun-style names (mz_env, mz_progress) and verb_noun names (mz_read_setup, mz_dfs_read), but this does not cause confusion.

    Tool Count4/5

    15 tools is at the upper edge of the typical well-scoped range, but each tool serves a distinct purpose across discovery, execution, monitoring, and post-processing. The four job-monitoring tools are individually justified by the async nature of simulations, though the count feels slightly heavy.

    Completeness4/5

    The set covers the full simulation workflow: environment discovery, project scanning, setup parsing, single/batch/toolbox execution, progress/status/log monitoring, job termination, and result reading/plotting. Notable gaps include the inability to create or edit setup files and a lack of result export or cleanup operations, but these can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources