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
      A
      quality
      A
      maintenance
      Enables AI assistants to interact with bridge structural analysis software for modeling, construction stages, and code checking.
      15
      229 PyPI
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      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
      9
      MIT

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: discovery/guidance (discover_api, read_skills), instance/connection inspection (get_status, list_instances), and execution (execute_code). Although get_status and list_instances both report version/path details, their core purposes—checking a specific connection vs. enumerating running instances—are clearly differentiated by the descriptions.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: discover_api, get_status, execute_code, list_instances, read_skills. There are no deviations in style or casing.

    Tool Count5/5

    Five tools are well-scoped for an MCP server that bridges to OpenSTAAD via code execution. Each tool serves a necessary part of the workflow: guidance discovery, connection/instance management, and code execution.

    Completeness5/5

    The surface covers the full lifecycle for this server's purpose: discovering API guidance, reading skills, checking connection/status, listing available STAAD.Pro instances, and executing Python against the OpenSTAAD API. No obvious operational gaps remain for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week