Openstaad Mcp

Name: Openstaad Mcp
Author: BentleySystems

by BentleySystemscommunityv1.1.2

An MCP server for Bentley STAAD.Pro that lets AI clients inspect connected STAAD.Pro instances and interact with models using the OpenSTAAD API. It supports tasks like discovering API guidance, listing instances, checking status, and executing validated Python code against a model.

From the registry: MCP server for Bentley STAAD.Pro via the OpenSTAAD API

GitHub Repository

Install & configure

Prerequisites

required
Windows 11 or newer
The server requires Windows 11 or newer.
required
STAAD.Pro 2025 or newer installed and running
Install Bentley STAAD.Pro 2025 or newer and have it running with a model open before using the server.
https://www.bentley.com/software/staad/
required
Install uv
Install uv to run the server via uvx, which is the recommended portable setup path.
```
$ powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
```
https://docs.astral.sh/uv/getting-started/installation/

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `openstaad-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Windows 11 or newer** — The server requires Windows 11 or newer.
- **STAAD.Pro 2025 or newer installed and running** — Install Bentley STAAD.Pro 2025 or newer and have it running with a model open before using the server. (https://www.bentley.com/software/staad/)
- **Install uv** — Install uv to run the server via uvx, which is the recommended portable setup path. Run: `powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"` (https://docs.astral.sh/uv/getting-started/installation/)

Canonical MCP server config (stdio transport):
- command: `uvx`
- args: ["--from","git+https://github.com/BentleySystems/openstaad-mcp","openstaad-mcp"]

Note: The README documents both stdio and HTTP transports. The simplest canonical configuration is stdio using uvx. For HTTP mode, start the server with args ["--from","git+https://github.com/BentleySystems/openstaad-mcp","openstaad-mcp","--transport","http"] and optionally add ["--port","<your-port>","--token","<your-token>"] when launching it. Clients then connect to the runtime URL (for example, the default endpoint pattern is http://127.0.0.1:<your-port>/mcp) and send the header Authorization: Bearer <your-token>. If no token is provided, the server auto-generates one and prints it to the terminal.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: The README documents both stdio and HTTP transports. The simplest canonical configuration is stdio using uvx. For HTTP mode, start the server with args ["--from","git+https://github.com/BentleySystems/openstaad-mcp","openstaad-mcp","--transport","http"] and optionally add ["--port","<your-port>","--token","<your-token>"] when launching it. Clients then connect to the runtime URL (for example, the default endpoint pattern is http://127.0.0.1:<your-port>/mcp) and send the header Authorization: Bearer <your-token>. If no token is provided, the server auto-generates one and prints it to the terminal.