HydroStar MCP
Related Servers
Alternatives to HydroStar MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to set and inspect parametric motor-mount designs, run modal and static finite-element analyses, generate mode-shape and stress plots, perform parameter sweeps, and check mesh convergence through natural language.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to perform native hull model I/O, Lackenby transformation, section generation, hydrostatics calculations, DXF linesplan export, and CSV/XLSX reporting on Windows without desktop automation.GPL 3.0
- 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
- AlicenseAqualityCmaintenanceModel Context Protocol (MCP) server for offshore robotics, AUV bathymetric survey planning, API 17D / ISO 13628-8 ROV rotary valve intervention interfaces (Class 1 to 7), DNV-RP-B401 cathodic protection evaluation, and ASME PCC-1 subsea bolted flange preloads.46 npmMIT
- 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
- AlicenseCqualityBmaintenanceEnables natural-language automation of LS-PrePost preprocessing and postprocessing by exposing tools that build and verify shell meshes, query nodes, parts and connectivity, run native commands, SCL and in-application Python, and read d3plot/binout results through pluggable backends. Every job runs in its own directory and returns an ID, status, log and artifacts, so results stay traceable and failures are never silently reported as success.30MIT
TDQS
Scored across 12 tools
The tools mostly map to distinct stages of the HydroStar workflow, from environment/geometry inspection through case preparation and result reading. A few boundaries could still be confused, especially generate_inputs versus prepare_case and make_reference_case versus plan_case, though the descriptions provide clarifying context.
Most tool names follow a consistent snake_case verb_noun pattern such as inspect_environment, build_geometry, plan_case, and read_rao. The main deviation is case_status, which lacks a verb and breaks the otherwise predictable pattern.
Twelve tools are well-scoped for a multi-stage engineering workflow involving inspection, geometry building, planning, execution, monitoring, and results retrieval. Each tool appears to earn its place without obvious redundancy or excessive breadth.
The surface covers the core lifecycle from environment inspection and geometry setup through case execution, cancellation, and RAO retrieval. Minor gaps exist around listing existing cases or cleaning up completed cases, which agents may need to work around.