MCP server enabling AI tools to interact with running Dlubal structural analysis applications (RFEM 6, RSTAB 9, RSECTION 1)
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"dlubal-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# dlubal-mcp **Model Context Protocol (MCP) server** that enables AI tools and large language models (LLMs) to interact with running [Dlubal](https://www.dlubal.com) structural analysis applications. Built on top of the [dlubal.api](https://pypi.org/project/dlubal.api/) gRPC client library, `dlubal-mcp` exposes tools that AI assistants can call directly to do modelling, analysis or reading results through the API scripts. ## Supported Applications | Application | Script Tool | |---|---| | **RFEM 6** — Finite Element Analysis | `run_rfem_script` | | **RSTAB 9** — Frame and Truss Analysis | `run_rstab_script` | | **RSECTION 1** — Cross-Section Analysis | `run_rsection_script` | ## How It Works ### HTTP access protection Starting with 1.0.13, HTTP access always requires a separate bearer token and a numeric loopback bind address. The matching Dlubal Connector provisions this automatically. Standalone clients must configure `DLUBAL_MCP_ALLOWED_API_KEYS` and send `Authorization: Bearer <access-token>`; the Dlubal application API key is a separate credential. Anonymous operation and query-string tokens are not supported. See [HTTP authentication and upgrade notes](docs/http-authentication.md). `dlubal-mcp` acts as a bridge between an AI assistant and a running Dlubal application. The application must already be open and its API service active — the MCP server connects to the live session, it does not launch applications itself. 1. Start RFEM 6, RSTAB 9, or RSECTION 1 on your machine 2. Launch the MCP server with proper settings (urls, API ports) 3. An AI tool calls e.g. `run_rfem_script` with Python code 4. The code executes against the live application and returns the output ### LLM Responsibility for API Scripts The `run_rfem_script`, `run_rstab_script`, and `run_rsection_script` tools execute arbitrary Python code against the live application. **The LLM is responsible for composing correct and valid API scripts** — the MCP server simply runs whatever code i…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.