Skip to main content
Glama
OpenSTAAD MCP Server

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
      1
      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.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read, query, compare, edit, QA/QC, and export RISA-3D .r3d structural models through natural language, with a standalone CLI for local diagnostics and reporting.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to drive desktop CAD software through natural language with verified execution, failure recovery, and traceable results across modeling, assemblies, drawings, exports, motion, FEA, and related engineering workflows.
      MIT
    • 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

    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
    ResponsivenessLimited data