Skip to main content
Glama
BentleySystems

OpenSTAAD MCP Server

Official
by BentleySystems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
discover_apiA

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_skillsA

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_instancesA

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.

get_statusA

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, model path, and the directories execute_code may currently read/write (allowed_dirs) — call this again after the user reconfigures allowed directories, since the MCP server must be relaunched for that change to take effect and a stale in-context list will otherwise look correct.

execute_codeA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

Resources