Discover available API guidance and skills.

Call this FIRST before using other openstaad-mcp tools. Then use read_skills with one or more specific skill names to load full guidance.

Read one or more skills by name.

Use discover_api first to list available skills. Each skill provides domain-specific guidance (e.g. analysis, geometry, loads).

Pass skill names like ["staad-analysis"] or sub-paths like ["staad-steel-design/assets/DESIGN_CODES"] to read reference files within a skill.

List all running STAAD.Pro instances.

Returns a list of instances with their alias, process ID, currently open file path, and STAAD version. Call this before execute_code when multiple STAAD instances may be running so you can pick the right one. The alias (e.g. staadPro1) is stable for the server session even if the model file changes.

If a version is below the minimum supported (25.0.1), a warning field is included with details about potential data inaccuracies.

Check the connection to a STAAD.Pro instance.

Pass instance (alias from list_instances) to target a specific instance. Omit it when only one instance is running.

Returns connection state, STAAD version, and model path.

Execute Python code in a sandbox against the OpenSTAAD API (don't forget to call discover_api and read_skills for API guidance).

The sandbox provides pre-connected staad (the OpenSTAAD root object) and input_data (if input_data_path is provided) variables (plus json and math modules). import statements, dir(), getattr(), ... are BLOCKED.

The last expression value or an explicit result = ... assignment is returned as the result. If output_data_path is provided, the sandbox will write the result to the specified file.

Paths must be on the user LOCAL filesystem and inside MCP roots or configured allowed_dirs. On Claude Desktop, users can configure allowed directories in the extension settings and Claude can use the filesystem copy_file_to_claude tool to move files to Claude's filesystem.