Skip to main content
Glama

Related Servers

Alternatives to simintech-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a running SOLIDWORKS session through its COM API, with tools for sketching, feature creation, assemblies, and visual feedback via screenshots.
      22
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to drive LIRA-SAPR/LIRA-FEM on Windows through its COM API, including creating and editing models, running analyses, and reading results with full tables exportable to CSV or Excel.
      41
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate CAD/CAE/CFD and chemical/mechanical engineering workflows through 60 JSON-RPC tools, including direct COM control of SolidWorks, Aspen Plus, HYSYS, AutoCAD, and Fluent, plus headless Linux first-principles solvers with invariant circuit breaking.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI assistant to control KOMPAS-3D through its COM API, including opening and saving documents, building parts and assemblies, measuring models, and creating dimensioned drawings.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control MATLAB Simulink models through natural language, providing tools for model creation, block management, wiring, simulation, and more via a local MCP backend.
      4
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to read and write .mph model files, control the COMSOL desktop GUI in real time, and run complete modeling, meshing, solving, and post-processing workflows.
      23
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool addresses a distinct resource or action: signals are separated from block parameters, reading files is separated from reading signals, and run/step/stop are clearly differentiated. Even adjacent tools like get_signal, read_output_file, and summarize_output_file have explicit usage boundaries, so an agent is unlikely to select the wrong one.

    Naming Consistency4/5

    The dominant pattern is snake_case verb_noun (get_signal, create_project, set_block_param, list_blocks), which is readable and predictable. A few tools break the pattern with bare verbs (connect, run, step, stop) or noun-style names (status, help_text), but these deviations are minor and do not obscure meaning.

    Tool Count3/5

    24 tools sits in the heavy borderline range; the set is organized into project, model, simulation, and results subdomains, but several utility/introspection tools (help_text, status, inspect_project_file, summarize_output_file) inflate the count. Each tool is individually useful, but the overall surface is more than a typical well-scoped MCP server needs.

    Completeness3/5

    The core workflow—create/open/save/close projects, add and configure blocks, run/step/stop, and fetch results—is covered. However, there is no way to delete a block or remove a wire, which is a notable gap when composing models iteratively, and signal-DB setup is also outside the tool surface. These gaps are workable but prevent full lifecycle coverage.

    Maintenance

    ActivityActive
    ResponsivenessSyncing