Skip to main content
Glama
miziyo

Ansys Research Runner MCP

by miziyo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Ansys Research Runner MCP

No user-submitted related servers found.

    Related Servers

    • bourne mcp

      KozakHou
      A
      license
      A
      quality
      A
      maintenance
      Provides MCP access to plan and execute reproducible computational experiments with immutable execution plans, artifact provenance, verification checks, and support for direct, Slurm, and PBS backends.
      20
      17
      Apache 2.0

    • Ansys Workbench MCP

      Chen-Xin-Yuan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Codex to control Ansys Workbench and ICEM CFD locally, executing scripts, managing projects, and running simulations.
      2
      MIT

    • Open Science MCP

      imjszhang
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to control the local Open Science research application, including creating projects, starting or continuing research sessions, inspecting progress and plans, canceling runs, and reading generated artifacts.
      12
      Apache 2.0

    • FEP Agent Hub

      S2mon123
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables evidence-first CAE automation on Windows through local MCP servers for FreeCAD, Elmer FEM, and ParaView, supporting validated workflows from CAD to simulation and post-processing with a shared safety and evidence runtime.
      3
      MIT

    • grant-agent-harness

      YPCC
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables reviewing grant application text, running deterministic eval cases, and executing Office of Research Aid packet workflows through MCP.
      Apache 2.0
    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

    B3.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool maps to a distinct stage of the research-run lifecycle: environment check, geometry inspection, region resolution, validation, planning, execution, status, cancellation, summary, and artifact listing. Even adjacent tools like validate_run and plan_run are separated by validation versus immutable CAE-IR compilation.

    Naming Consistency4/5

    Tool names overwhelmingly follow a clear imperative snake_case verb_noun pattern (inspect_model, start_run, cancel_run, list_run_artifacts). The lone exception is doctor, a single-word diagnostic command that is conventional but breaks the pattern.

    Tool Count5/5

    Ten tools is well-scoped for the pipeline: four pre-execution/setup tools, three run-control tools, and three result/artifact tools. No tool feels redundant or out of place.

    Completeness5/5

    The set covers the full lifecycle from environment/model inspection through recipe validation and planning, run execution/status/cancellation, and post-run summary/artifact discovery. It deliberately avoids field-array transfer and recipe editing, which are likely outside the runner's scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources