Skip to main content
Glama
HanKin666

sentaurus-mcp

by HanKin666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to sentaurus-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-gds

      zesun33
      F
      license
      A
      quality
      B
      maintenance
      Enables AI agents to run GDSII stream-out, KLayout DRC, Netgen LVS, and Magic extraction via MCP.
      6
      -

    • COMSOL MCP Server

      HBPEKING-TKS
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization through the MCP protocol.
      78
      MIT

    • comsol-mcp-server

      Qwup2112
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization via the MCP protocol.
      MIT

    • AspenPlus MCP Server

      brack101
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Aspen Plus process simulations through a standardized MCP interface, supporting simulation control, data access, and flowsheet manipulation.
      32
      MIT

    • ABAQUS MCP Pro

      TutuBarry
      A
      license
      C
      quality
      A
      maintenance
      Enables AI assistants to control and automate Abaqus/CAE simulations via MCP, including model query, job management, ODB inspection, KPI extraction, capsule tracking, physics contract validation, report generation, and viewport capture. It also supports noGUI batch mode, dual transport, and integration with Codex/Claude clients.
      110
      1
      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.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: listing vs fetching experiment metadata, preparing vs launching an experiment, reading logs vs listing files. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (list_experiments, get_experiment, create_experiment, submit_experiment, read_log, list_artifacts). There is no mixing of conventions or vague verbs.

    Tool Count5/5

    Six tools is well-scoped for an experiment management server, covering the essential lifecycle without bloat. Each tool serves a clear, necessary role.

    Completeness4/5

    The surface covers the main workflow: create, submit, monitor (get/read_log), and list artifacts. Missing operations like delete/cancel or update are not explicitly present, but the core experiment lifecycle is well served and the absence is a minor gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources