OpenSTAAD MCP Server

io.github.BentleySystems由 GitHub 帳號 BentleySystems 發布v1.3.0更新於 Oct 24, 2026

MCP server for Bentley STAAD.Pro via the OpenSTAAD API

已驗證STDIO僅桌面開發者工具資料與分析

概覽

AI 產生的概覽

本機 MCP 伺服器，讓 AI 助理透過 OpenSTAAD API 讀取與修改 Bentley STAAD.Pro 結構模型。

可以做什麼
  • 探索並閱讀 STAAD.Pro OpenSTAAD API 的技能說明與使用指引
  • 列出執行中的 STAAD.Pro 實例及其模型路徑與版本，查詢連線狀態、版本與分析狀態
  • 對已連線的 STAAD.Pro 模型執行經驗證的 Python 程式碼，用於定義載重工況、設定屬性與擷取資料
  • 將 CSV 或 XLSX 輸入檔讀入沙箱，並把結果寫回 CSV 或多工作表 XLSX 檔案
適用情境
適合希望讓助理自動處理 STAAD.Pro 重複性工作的結構工程師，例如載重工況定義、屬性批次設定與資料擷取，也可同時處理多個已開啟的模型。
執行需求
需要 Windows 11 或更新版本，並已安裝且正在執行 STAAD.Pro 2025 或更新版本，且已開啟模型。可透過 Claude Desktop 安裝 .mcpb 擴充套件，或以 uv/uvx 在 stdio 模式本機執行；HTTP 模式預設監聽 18120 埠，需使用 Authorization Bearer 權杖。不需雲端帳號或 API 金鑰。
安裝前請注意
execute_code 工具會對實際模型執行 Python，可能寫入載重工況、屬性與模型資料；程式碼會經 AST 檢驗並封鎖匯入、檔案存取與危險內建函式，但仍應在核准前確認操作內容。檔案讀寫僅限設定的允許目錄，上限為 50 MB、10 萬列與 500 欄，預設不覆寫既有輸出檔。HTTP 模式下應妥善保管 bearer 權杖並讓端點僅限本機存取。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 OpenSTAAD MCP Server，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

OpenSTAAD MCP Server

A Model Context Protocol (MCP) server for Bentley STAAD.Pro that enables AI agents like Claude Desktop, Gemini, or VSCode Copilot to interact with your STAAD.Pro models and perform various time-consuming tasks like load cases definition, data extraction, repetitive property setting and more.

This MCP server was introduced as part of Bentley's Infrastructure AI Co-Innovation Initiative to help our users and accounts discover opportunities and innovate faster, while connecting Bentley's unique engineering tool capabilities to their emerging agentic workflows.

Key Features

  • Fast and flexible: Enjoy minimal latency, interact with every STAAD.Pro features covered by the OpenSTAAD API.
  • AI-friendly: Provides documentation, guidance and feedback via dedicated tools to help your AI agent ramp up quickly on the STAAD.Pro API.
  • Multi-instance support: Connects to multiple running STAAD.Pro instances simultaneously to parallelize tasks across models.
  • Privacy-first: All processing happens locally on your machine. No data is sent to the cloud. No telemetry.

Prerequisites

  • OS: Windows 11 or newer
  • STAAD.Pro 2025 or newer installed and running

Quick Start with Claude Desktop (<2min)

  1. Download the latest openstaad-mcp.mcpb file from the GitHub Releases page.
  2. Open Claude Desktop.
  3. Click the ☰ menu (top-left) → File → Settings → Extensions.
  4. Click Advanced → Install Extensions.
  5. Select the downloaded .mcpb file.
  6. Click the ☰ menu (top-left) → File → Exit
  7. Restart Claude Desktop.

Claude Desktop will install the server automatically. Open a new conversation and ask Claude to interact with your STAAD.Pro model.

Tip: Make sure STAAD.Pro is running with a model open before you start chatting.

Other Clients & Configuration

TL;DR:

If not already installed, install uv with the command:

powershell
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Configure your client to start the server in stdio mode with the command:

powershell
uvx --from git+https://github.com/BentleySystems/openstaad-mcp openstaad-mcp

VS Code with GitHub Copilot

  • For stdio: Open the Command Palette → MCP: Add Server... → Command (stdio) and enter the following command:

    powershell
    uvx --from git+https://github.com/BentleySystems/openstaad-mcp openstaad-mcp

  • For http: First, start the server in a terminal:

    powershell
    uvx --from git+https://github.com/BentleySystems/openstaad-mcp openstaad-mcp --transport http

    Look for the generated token and URL in the terminal output. It should look like this:

    WARNING: No --token provided. Auto-generated token: abc123def456ghi789jkl012mno345pqINFO:  Starting MCP server 'OpenSTAAD MCP' with transport 'http' (stateless) on http://127.0.0.1:18120/mcp

    Then, in VS Code, open the Command Palette → MCP: Add Server... → HTTP URL and enter the URL shown in the terminal (e.g. http://127.0.0.1:18120/mcp). 18120 is the default port, but yours may differ if you have multiple instances running or if you changed the default. Add the header Authorization: Bearer <token> with the token shown in the MCP server terminal.

GitHub Copilot CLI

Use the /mcp add command inside a Copilot CLI session to add the server. See the Copilot CLI documentation for more details.

  • For stdio transport, use the command:

    powershell
    uvx --from git+https://github.com/BentleySystems/openstaad-mcp openstaad-mcp

  • For HTTP transport, first start the server in a terminal:

    powershell
    uvx --from git+https://github.com/BentleySystems/openstaad-mcp openstaad-mcp --transport http

    Look for the generated token and URL in the terminal output. It should look like this:

    WARNING: No --token provided. Auto-generated token: abc123def456ghi789jkl012mno345pqINFO:  Starting MCP server 'OpenSTAAD MCP' with transport 'http' (stateless) on http://127.0.0.1:18120/mcp

    Then add the server in Copilot CLI using the URL shown in the terminal (e.g. http://127.0.0.1:18120/mcp). 18120 is the default port, but yours may differ if you have multiple instances running or if you changed the default. Add the header Authorization: Bearer <token> with the token shown in the MCP server terminal.

Claude Desktop (manual configuration)

If you prefer manual setup over the .mcpb bundle, edit the Claude Desktop config file directly:

  • Windows (MSIX): %LOCALAPPDATA%\Packages\Claude_<id>\LocalCache\Roaming\Claude\claude_desktop_config.json
  • Windows (classic): %APPDATA%\Claude\claude_desktop_config.json
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
jsonc
{  "mcpServers": {    "openstaad": {      "command": "uvx",      "args": ["--from", "git+https://github.com/BentleySystems/openstaad-mcp", "openstaad-mcp"]    }  }}

Claude Code (CLI)

  • For stdio transport, use the command:

    powershell
    claude mcp add --transport stdio openstaad -- uvx --from git+https://github.com/BentleySystems/openstaad-mcp openstaad-mcp

  • For HTTP transport, first start the server in a terminal:

    powershell
    uvx --from git+https://github.com/BentleySystems/openstaad-mcp openstaad-mcp --transport http

    Look for the generated token and URL in the terminal output. It should look like this:

    WARNING: No --token provided. Auto-generated token: abc123def456ghi789jkl012mno345pqINFO:  Starting MCP server 'OpenSTAAD MCP' with transport 'http' (stateless) on http://127.0.0.1:18120/mcp

    Then add the server in Claude Code with the command:

    powershell
    claude mcp add --transport http openstaad http://127.0.0.1:18120/mcp --header "Authorization: Bearer <your-token>"

    18120 is the default port, but yours may differ if you have multiple instances running or if you changed the default.

Gemini CLI

  • For stdio transport, use the command:

    powershell
    gemini mcp add openstaad uvx --from git+https://github.com/BentleySystems/openstaad-mcp openstaad-mcp

  • For HTTP transport, first start the server in a terminal:

    powershell
    uvx --from git+https://github.com/BentleySystems/openstaad-mcp openstaad-mcp --transport http

    Look for the generated token and URL in the terminal output. It should look like this:

    WARNING: No --token provided. Auto-generated token: abc123def456ghi789jkl012mno345pqINFO:  Starting MCP server 'OpenSTAAD MCP' with transport 'http' (stateless) on http://127.0.0.1:18120/mcp

    Then add the server in Gemini CLI with the command:

    powershell
    gemini mcp add --transport http --header "Authorization: Bearer <your-token>" openstaad http://127.0.0.1:18120/mcp

    18120 is the default port, but yours may differ if you have multiple instances running or if you changed the default.

Transport Modes

The server supports two transport modes:

ModeWhen to use
stdio (default)The MCP client launches the server process directly. Used by Claude Desktop, Claude Code, VS Code Copilot (stdio config).
HTTPThe server runs persistently and clients connect over the network.

CLI Options

FlagDefaultDescription
--transport {stdio,http}stdioTransport mode
--log-level LEVELINFODEBUG, INFO, WARNING, or ERROR
--log-file PATHOS defaultPath to log file
--port PORT18120[http] TCP port to listen on
--token TOKEN-[http] Bearer token for authentication

Available MCP Tools

ToolDescription
discover_apiLists available API skills and usage guidance
read_skillsReturns detailed guidance for requested skills
list_instancesLists active STAAD.Pro instances with model paths and versions
execute_codeRuns validated Python code against the connected STAAD.Pro model
get_statusReturns connection state, STAAD version, model path, analysis status

File I/O

The execute_code tool supports optional server-side file I/O for bulk data workflows. Instead of passing large datasets through the agent's context window, the server reads/writes CSV and XLSX files directly and injects the data into the sandbox as the input_data variable.

ParameterDescription
input_data_pathPath to a .csv or .xlsx file. The server reads and parses it, then injects as the input_data variable in the sandbox.
output_data_pathPath where the sandbox return value will be written. The return value must be a list-of-lists (CSV) or a {sheet_name: {columns, rows}} dict (multi-sheet XLSX).
overwriteAllow overwriting an existing output file (default false).

input_data has a stable, extension-specific shape:

  • CSV: a list of row lists. If a header is detected, it is input_data[0] and data rows start at input_data[1:].
  • XLSX: a dict: {sheet_name: {"columns": list, "rows": list_of_rows}}.

Path containment: File paths must resolve inside a configured allowed boundary before any read/write occurs. The server supports both client-configured MCP roots and server-configured allowed directories (via --allowed-dirs or user_config.allowed_directories in the manifest). The server validates paths against these boundaries before any file access.

Limits: Max file size 50 MB, max 100K rows, max 500 columns, max 50 input sheets.

Security Notes

  • Bearer token authentication. Pass --token MY_SECRET_TOKEN when running in HTTP mode and include Authorization: Bearer <token> in client requests.
  • DNS rebinding protection. Starlette Middlewares validate Host, Sec-Fetch-Site and Origin headers.
  • Code sandbox. The execute_code tool validates all Python code via AST analysis before execution. Imports, file access, and dangerous builtins are blocked.

Privacy Policy

Please find the Bentley Systems privacy policy here.

Contributing

See CONTRIBUTING.md for guidelines on setting up your development environment, branch naming, running tests, and submitting pull requests.

來源：README.md，提交 9910fef

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

2
  1. v1.3.0最新Oct 1, 2026
  2. v1.2.0Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分