Skip to content

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 22 Jun 12:32

Tekla MCP Server v0.4.0

Multi-version release. The live server is now a single universal build that works with any
installed Tekla Structures version (2021+)
— no more picking a version or downloading the
"right" zip. It also adds a developer tool for generating an offline Tekla Open API reference.

What's new since v0.3.0

Universal multi-version Tekla support

  • One build works with any installed Tekla 2021+. The server loads the Tekla Open API
    assemblies from your installed/running Tekla at runtime, so the version-locked protocol
    always matches the version you're running.
  • Auto-detects the running Tekla (TeklaStructures.exe). Override with the TEKLA_BIN_DIR
    environment variable if your install isn't found automatically.
  • The Windows download no longer bundles Tekla DLLs — one artifact for everyone.
  • Build overrides for advanced cases: -p:TeklaVersion= (compile baseline, from NuGet) and
    -p:TeklaBinDir= (compile against a local install).

Developer tooling

  • tools/TeklaApiDoc — a cross-platform generator (metadata-only, via MetadataLoadContext)
    that emits a grep-friendly Markdown reference of the Tekla Open API for offline signature
    verification. Output is git-ignored (Trimble content); regenerate locally. See
    tools/TeklaApiDoc/README.md.

Why this release

Earlier builds were pinned to one Tekla version (2023) and silently failed to connect to other
versions. This release removes that friction entirely: install once, run against whatever Tekla
version is open.

Downloads

Asset Use case
TeklaMcp.Server-0.4.0-net48-win-x64.zip Production — Windows + Tekla Structures 2021+ with an open model (universal; loads the matching Tekla DLLs at runtime)
TeklaMcp.Server-0.4.0-net8.0-mock.zip Development / testing without Tekla

Requirements

Windows + Tekla (net48):

  • Windows x64
  • Tekla Structures 2021 or newer, running with a model open
  • .NET Framework 4.8 runtime
  • If the server can't find Tekla automatically, set TEKLA_BIN_DIR to the Tekla bin folder

Mock backend (net8.0):

MCP client configuration

Extract the zip, then point your MCP client to the executable:

{
  "mcpServers": {
    "tekla": {
      "command": "C:\\path\\to\\TeklaMcp.Server.exe"
    }
  }
}

Keep the .exe and all .dll files in the same directory.

Full changelog

See CHANGELOG.md.