OpenSTAAD MCP Server
Related Servers
Alternatives to OpenSTAAD MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to interact with Bentley STAAD.Pro models for tasks like load case definition, data extraction, and property setting through natural language.554MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to interact with bridge structural analysis software for modeling, construction stages, and code checking.1517 PyPI1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables 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.1MIT
- AlicenseBqualityCmaintenanceAn agentic MCP server for CSI ETABS v22+ that enables AI agents to model, load, analyze, design, and inspect building structures through 60 curated engineering tools and live .NET reflection of the full 1,293-method OAPI. Includes offscreen 3D rendering of deformed shapes and D/C ratios, interactive database table editing, and background analysis execution.7120Apache 2.0
- AlicenseAqualityAmaintenanceEnables an AI assistant to drive a running CSiBridge session by calling its full COM API — building and editing models, reading signatures and enums, running analyses, and reading or editing database tables of definitions and results. Access is available locally over stdio or remotely over HTTPS with per-person tokens, and a mock backend supports development off Windows.15Functional Source , Version 1.1, MIT Future
- AlicenseBqualityBmaintenanceEnables 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.41MIT
TDQS
Scored across 5 tools
Each tool has a distinct purpose: discover_api and read_skills are clearly sequential for API guidance, while list_instances and get_status differ in scope (all instances vs. specific connection status). The only slight overlap is between these instance-related tools, but descriptions clarify the difference.
All tool names follow a consistent verb_noun pattern (discover_api, read_skills, list_instances, get_status, execute_code), making the API predictable and easy to navigate.
Five tools is well-scoped for the server's purpose, covering the essential workflow from discovery and guidance to instance management and code execution without unnecessary bloat.
The tool set covers the full workflow from discovering skills to executing code, with instance listing and status checks. Minor gaps like managing STAAD instance lifecycle (open/close) may exist but appear outside the server's intended scope.