Skip to main content
Glama
BentleySystems

OpenSTAAD MCP Server

Official

Related Servers

Alternatives to OpenSTAAD MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Bentley STAAD.Pro models for tasks like load case definition, data extraction, and property setting, running locally with multi-instance support and no cloud dependency.
      5
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to interact with bridge structural analysis software for modeling, construction stages, and code checking.
      132
      58 PyPI
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding assistants to directly control CSI ETABS for structural and seismic analysis, including model inspection, material/section definition, frame generation, solver execution, and result extraction through natural language.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-driven interaction with Tekla Structures through natural language commands, allowing users to select elements, insert components, and automate modeling workflows.
      12
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with Autodesk Civil 3D through natural language, supporting tools for surfaces, alignments, profiles, corridors, pipe networks, COGO points, and AutoCAD geometry.
      9
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to CSI ETABS for structural engineering tasks, enabling model creation, analysis, design, and seismic checks via the COM API.
      69
      4
      MIT

    TDQS

    A4.6/5.0

    Scored across 5 tools

    Disambiguation4/5

    discover_api and read_skills are sequential but distinct; list_instances and get_status both report instance state, though one enumerates all instances and the other checks a single connection. No severe ambiguity.

    Naming Consistency5/5

    All five tools follow a consistent verb_noun snake_case convention (discover_api, read_skills, list_instances, get_status, execute_code), making the pattern predictable.

    Tool Count5/5

    Five tools is well-scoped for an API execution server: discovery, guidance, instance listing, status check, and code execution. Each tool has a clear role.

    Completeness4/5

    The workflow from discovering guidance to executing code is covered. Minor gap: no explicit instance selection parameter on execute_code and no model lifecycle tools, but the API sandbox can handle those operations.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week