v0.7.0

Tekla MCP Server v0.7.0

This release turns the three most painful workarounds from a real end-to-end modeling session
into first-class MCP tools — IFC/reference geometry, beam Position, and custom Connections —
and adds the first broad Drawing API surface. Agents can now work from drawing-list QA through
view/annotation editing without using tekla_run_csharp for routine operations.

The drawing layer is experimental. This is its first release and it has seen far less
live-model testing than the model tools. Individual tools may fail on drawing states or
object types that have not been exercised yet — Tekla's Drawing API has version-specific
remoting/serialization quirks. Preview-by-default and Ctrl+Z still apply; please report
failures via tekla_report_gap or a GitHub issue.

Highlights

• IFC/reference objects are inspectable. tekla_get_reference_geometry accepts the current
  selection or Tekla integer IDs and returns external/IFC GUID, entity type, dimensions,
  reference-model source, world AABB, capped attributes and capped face polygons. This avoids
  parsing the IFC file from disk merely to locate a selected opening.
• Beam Position is first-class. tekla_create_beam and tekla_modify_part now support
  Plane/Rotation/Depth and their offsets. matchPositionGuid copies Position from a known-good
  exemplar, with explicit fields acting as overrides.
• Connections no longer require C# scripts.
  • tekla_list_connections reads the exact component name (including Cyrillic), number,
    primary/secondary GUIDs, UpVector, direction and status.
  • tekla_create_connection creates system/custom connections.
  • tekla_copy_connection carries an exemplar's identity/orientation to new parts.
  • Pending geometry is committed before component insertion, closing the fresh-part race seen
    during field use.
• Less tool-call overhead. tekla_create_beams creates up to 200 structured beam specs in
  one preview/apply batch.
• Geometry helpers. tekla_get_solid_bbox makes native-part face-plane checks explicit;
  tekla_list_control_lines returns control-line endpoints.
• API-reference diagnostics. tekla_get_api_reference_status says whether offline docs are
  ready and gives exact setup guidance when they are not.
• The drawing list is queryable without opening drawings. New tools list/filter rows and
  Drawing List selection, summarize types/statuses, find stale or issued-but-modified drawings,
  and return the model identifiers represented by a drawing.
• Drawing lifecycle is first-class and previewable. Agents can preview/apply open, save,
  close, create, batch create, edit metadata/status flags, delete, issue, unissue, update,
  auto-place views, and export PDFs. Assembly, single-part, cast-unit, GA, and saved
  AutoDrawing-rule workflows are covered.
• The active drawing is inspectable and editable. View and drawing-object tools expose
  best-effort ID/ID2 addressing, model GUID links, geometry, visibility, optional UDAs, and
  editor selection. Agents can create and edit:
  • front/top/back/bottom/3D, straight/curved section, and detail views;
  • GA model views from explicit global view/display coordinate systems and restriction bounds;
  • text, lines, rectangles, circles, arcs, polylines, polygons, revision clouds, and symbols;
  • straight, angle, radius, radial curved, and orthogonal curved dimensions;
  • object marks and level marks, including merge/split operations for compatible marks.
• Drawing coordinates are explicit. Content specs choose view, model, or sheet;
  global model points are transformed through the target view, while sheet origins and
  dimension distances use paper millimetres. tekla_get_drawing_sheet supplies actual and
  configured sheet bounds for placement.
• The C# joker is easier to review and reaches more APIs. tekla_check_csharp runs the same
  policy/compiler path without execution and returns the source SHA-256 plus detected mutations.
  Live scripts reference all installed managed Tekla.Structures*.dll assemblies. Drawing is
  intentionally used through an explicit alias such as
  using TSD = Tekla.Structures.Drawing; to avoid Part/View name collisions.

All persistent mutations remain preview-by-default. Drawing, view, and drawing-object writes
attempt the same MCP_ORIGIN tagging, although support for drawing-side UDAs varies by object
type and environment.

Drawing workflow and preconditions

The Drawing API is stateful. The intended sequence is:

1. Call tekla_get_drawing_status and tekla_list_drawings.
2. Use the opaque drawing key returned by the list. Exact mark lookup is accepted only when it
   is unambiguous.
3. Close the editor before creating drawings. A drawing being updated, deleted, or printed
   must not be active; updating also requires up-to-date numbering.
4. Open one drawing before listing/editing views and drawing objects.
5. Call each mutating tool with its default apply=false, inspect the preview, then repeat with
   apply=true only after approval.
6. Re-list views/objects after inserts or deletes. Indices are display aids, not persistent
   identities.

Drawing keys normally use DrawingInternal ID/ID2. Because that surface is version-sensitive,
the backend falls back to a composite of public type/model/sheet/mark/name properties when the
identifier is unavailable. Treat drawing, view, and object IDs as best-effort until verified on
the target Tekla version.

Coordinate spaces are deliberately not mixed:

• view: local to the target view/display coordinate system;
• model: global model millimetres transformed into the target view;
• sheet: paper millimetres on the drawing sheet (viewIndex=-1, no viewId).

View insertion/origin/frame values and dimension-line offsets are paper millimetres. Section
cut/detail points are source-view-local; section depths are model millimetres.

Validation

• Tool registration inventory: 100 unique tekla_* tools, including 51 drawing-specific tools.
• Mock-only automated suite: 79 tests.
• Full solution compiles against the version-matched Tekla 2021 Model + Drawing packages.
• The earlier modeling phase passed MCP stdio initialize/tools-list and structured batch-preview
  smoke tests.

No live Windows drawing-editor validation is claimed here.

Live-validation notes

The new drawing calls are based on the common Tekla 2021 Drawing API surface and are wrapped to
degrade with messages/errors instead of crashing a whole batch. They still need validation on
Windows with each supported Tekla generation before being called fully proven:

• reference-object metadata keys and world face coordinates on rotated/scaled/base-point IFCs;
• custom Connection insertion/status and attributes-file behavior;
• Position LEFT/RIGHT and FRONT/BEHIND behavior against known model faces;
• DrawingInternal.DatabaseObjectExtensions ID/ID2 extraction and fallback-key behavior;
• drawing-list selection and active-editor transitions;
• assembly/single-part/cast-unit/GA insertion and saved AutoDrawing rules;
• update/issue/delete/place-view operations and their exact editor/numbering preconditions;
• PDF printer enums, output naming, and paths;
• view creation/rotation, global-model-to-view conversion, paper placement, and dimensions;
• drawing-object UDA support and MCP_ORIGIN persistence by object type;
• mark merge/split compatibility and resulting Mark/MarkSet identities;
• defining-point geometry for complex dimension sets, level marks, symbols, and model-linked
  drawing objects (the generic reader currently degrades to identity/bounding boxes);
• saved view/object/mark attribute files in real firm/project environments.

Reference geometry degrades to partial metadata/messages if a version or exporter lacks a field.
Arbitrary custom-component attributes are not enumerable in a reliable generic way; pass an
attributesFile when copying a parameter set.

Drawing view/object enumeration indices are ephemeral. The DrawingInternal IDs can be absent on
some versions or objects; if so, use a fresh listing/selection rather than retaining indices
across edits. AutoDrawing/printing/attributes are resolved by Tekla and remain
environment-specific.

tekla_replicate_detail is not in this release. It should be built after the new Position and
Connection primitives have passed live validation, so the high-level workflow does not hide
low-level placement errors.

v0.6.0

Tekla MCP Server v0.6.0

Two big changes. Releases are now built per Tekla version — download the zip matching your Tekla (2021–2026); the wrong one fails fast with a clear message instead of cryptic remoting errors. And agents get a policy-checked C# scripting escape hatch (tekla_run_csharp) for Tekla Open API capabilities that have no dedicated tool yet.

⚠️ Pick the right zip

The universal single-exe build is gone (#11) — it silently broke on machines with stale Tekla assemblies in the GAC (#7). Each zip below is compiled for one Tekla version:

Asset	For
TeklaMcp.Server-v0.6.0-tekla2021.zip	Tekla Structures 2021
TeklaMcp.Server-v0.6.0-tekla2022.zip	Tekla Structures 2022
TeklaMcp.Server-v0.6.0-tekla2023.zip	Tekla Structures 2023
TeklaMcp.Server-v0.6.0-tekla2024.zip	Tekla Structures 2024
TeklaMcp.Server-v0.6.0-tekla2025.zip	Tekla Structures 2025
TeklaMcp.Server-v0.6.0-tekla2026.zip	Tekla Structures 2026
TeklaMcp.Server-0.6.0-net8.0-mock.zip	Development / testing without Tekla (mock backend)

The Tekla DLLs themselves are not bundled — they load at runtime from your installed Tekla, after the server verifies the version matches its build. On a mismatch, every Tekla operation returns "Wrong build for this Tekla version … download …-tekla<year>.zip". Stale GAC copies of a different Tekla version can no longer hijack the process.

What's new since v0.5.0

Per-Tekla-version builds (#11)

• TeklaAssemblyResolver rewritten policy-free: locate the installed Tekla's bin (TEKLA_BIN_DIR → running TeklaStructures.exe → registry, preferring the install matching the build), verify the major version, Assembly.LoadFrom. No binding redirects, no byte-loading.
• The "server started before Tekla" flow still recovers without a restart, and the remoting-channel auto-alignment (…-Console:<version> pipes) from v0.5.0 is unchanged.
• Building from source now takes -p:TeklaVersion=<NuGet version> (e.g. 2023.0.1); CI compiles the whole 2021–2026 matrix on every PR.
• Verified live on Tekla Structures 2023 (80k+-object model) on a machine where the universal build previously failed.

C# scripting escape hatch (#10)

• tekla_run_csharp — run a short C# script against the live model: Roslyn scripting, Tekla namespaces pre-imported, Print(...) for output, the last expression returned as JSON. Pipeline: syntax-level safety policy → compile → execute, with every failure reported back so the agent can self-correct.
• tekla_search_api / tekla_get_api_doc — offline search over the locally generated Tekla Open API reference (tools/TeklaApiDoc), so agents verify signatures instead of guessing them.
• Safety: read-only by default — mutating members require allowMutations=true, which the agent must only set after showing you the script and getting your explicit go-ahead. No file/network/process/reflection/thread/Console access, no #r/#load, hard timeout, capped output. This is a barrier for well-behaved agents, not a security sandbox.
• New MCP server instructions give agents an escalation ladder: dedicated tools → script escape hatch → tekla_report_gap.

Requirements

Windows + Tekla (net48):

• Windows x64
• Tekla Structures 2021–2026, running with a model open — with the matching zip from above
• .NET Framework 4.8 runtime
• If the server can't find Tekla automatically, set TEKLA_BIN_DIR to the Tekla bin folder
• If connection fails with Tekla open, check the error message: it lists the published Tekla pipes; set TEKLA_MCP_CHANNEL to the exact pipe name if needed

Mock backend (net8.0):

• .NET 8 runtime

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, all .dll files and TeklaMcp.Server.exe.config in the same directory.

Full changelog

See CHANGELOG.md.

v0.5.0

Tekla MCP Server v0.5.0

Reliability and scale release. The live server now connects to Tekla setups where the Open API
channel is published under a non-default name (and no longer trips over stale Tekla assemblies
in the GAC), and the whole-model tools are fast enough for 400k+-object models. Agents also
get a formal way to report missing capabilities.

What's new since v0.4.0

Connection fixes for real-world Tekla setups (issue #7)

• Some Tekla installations publish the Open API remoting pipe as
  Tekla.Structures.Model-Console:<version> instead of the default
  Tekla.Structures.Model-:<version> — the server previously reported "Not connected" even
  though Tekla was open. It now probes the machine's named pipes before the first connection and
  targets the channel Tekla actually publishes. Override with the TEKLA_MCP_CHANNEL env var.
• If the compile-baseline Tekla assemblies (2021) were installed in the GAC, .NET silently
  loaded them and spoke the wrong protocol version to the running Tekla. The universal build now
  always loads the Open API DLLs from your installed/running Tekla, never from the GAC.
• "Not connected" errors now include real diagnostics: the client channel name, the loaded API
  version and where it was loaded from, and the Tekla model pipes present on the machine.

Large-model performance (issue #5)

On a ~420k-object model, tekla_count_objects used to take ~10 minutes and
tekla_get_model_summary ran until the MCP client dropped the connection (-32000). Now:

• Object data is fetched in batches during enumeration (AutoFetch) instead of one remoting
  round-trip per property read.
• Scans match on cheap direct properties first and read report properties / solids only for the
  objects actually returned. GetSolid() — the most expensive Open API call — is no longer
  executed per object on whole-model paths.
• An unfiltered tekla_count_objects returns instantly (enumerator size, no object walk).
• tekla_get_model_summary streams cheap reads, and gains options for huge models:
  includeWeights=false (skip the per-part weight lookup) and maxObjects (cap the scan; the
  result is marked truncated).
• Type-filtered queries (Beam, PolyBeam, ContourPlate, Grid) pre-filter at the Tekla API
  level via GetAllObjectsWithType.

Gap reporting for agents

• MCP server instructions now steer connecting agents to work with the provided tools and to
  report missing functionality instead of scripting around it or fabricating data.
• New tool tekla_report_gap — produces a ready-to-file GitHub issue draft (title + body) for a
  missing capability, logs the request locally, and points to the issues URL (configurable via
  TEKLA_MCP_ISSUES_URL). The server never files issues itself.

Downloads

Asset	Use case
TeklaMcp.Server-0.5.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.5.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
• If connection still fails with Tekla open, check the error message: it lists the published
  Tekla pipes; set TEKLA_MCP_CHANNEL to the exact pipe name if needed

Mock backend (net8.0):

• .NET 8 runtime

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, all .dll files and TeklaMcp.Server.exe.config in the same directory —
the config is required for correct Tekla assembly resolution.

Full changelog

See CHANGELOG.md.

v0.4.0

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):

• .NET 8 runtime

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.

v0.3.0

Tekla MCP Server v0.3.0

The first release that can write to the model. Alongside reading and analysis, agents can now create, edit and delete objects — with a preview-by-default safety model — so prompts like "generate a frame", "fix the crooked columns" or "re-orient the flipped columns" map directly to tools instead of ad-hoc scripts.

What's new since v0.2.2

Geometry / grids

• tekla_list_grids — list grid lines (axis, label, coordinate)
• tekla_resolve_point — translate axis labels + elevation (e.g. 1 × Д × 6000) into model coordinates

Write primitives

• tekla_create_beam, tekla_create_column, tekla_create_plate
• tekla_modify_part (profile / material / class / name / endpoints)
• tekla_swap_handles
• tekla_delete_objects (by filter or GUID list)

Generators

• tekla_generate_frame — a full bayed frame (columns + per-story beams)
• tekla_create_column_grid — columns at every X×Y intersection
• tekla_create_beam_between_grids — a beam between two grid intersections at an elevation

Find & fix

• tekla_straighten_columns — re-plumb crooked columns
• tekla_fix_column_handles — re-orient flipped columns (modeled as beams)

Safety model

• Preview-by-default: every mutating tool takes apply (default false) and returns a plan (counts + preview) without changing anything. Pass apply=true to commit.
• Created/modified objects are tagged with the MCP_ORIGIN user-defined attribute, so agent output is findable and revertible. Tekla Ctrl+Z also undoes commits.
• Filter-based mutations are capped by a limit (default 200).
• The Tekla backend forces the global coordinate system around writes so coordinates are interpreted as global model millimetres.

Notes

• Verified against a live Tekla model; grid coordinate parsing now supports repeat syntax (e.g. 4*6000).
• Coordinates are global model coordinates (mm).

Example use cases

• "Generate a 3×2 bay frame, 6 m bays, 4 m story height, HEA300 columns / IPE300 beams — preview first."
• "Find columns that aren't plumb and straighten them."
• "Find columns modeled as beams with inverted handles and fix them."
• "Create a beam between axes 1 and 2 along axis Д at +6.000."

Downloads

Asset	Use case
TeklaMcp.Server-0.3.0-net48-win-x64.zip	Production — Windows + Tekla Structures with an open model
TeklaMcp.Server-0.3.0-net8.0-mock.zip	Development / testing without Tekla

Requirements

Windows + Tekla (net48):

• Windows x64
• Tekla Structures 2023+ (validated workflow)
• Tekla running with a model open
• .NET Framework 4.8 runtime

Mock backend (net8.0):

• .NET 8 runtime

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.

v0.2.2

Tekla MCP Server v0.2.2

A capability release that broadens read/analyze coverage: assembly-level analytics, a model-quality (QA) check battery, a generic property reader, table export, and a selection-scope switch shared across the query and analytics tools.

What's new since v0.2.1

New tools

• tekla_get_properties — read any named properties (report properties, UDAs, or built-ins like VOLUME/AREA/WEIGHT) for an object by GUID, without a dedicated tool per field
• tekla_export_objects — export filtered objects as a CSV or Markdown table (bill-of-materials handoff)
• tekla_list_assemblies — assembly marks (ASSEMBLY_POS) with part count and total weight per mark
• tekla_count_assemblies — count distinct assembly marks (unique assembly types)
• tekla_get_assembly_parts — list all parts sharing a given assembly mark
• tekla_find_modeling_issues — QA battery (missing material/profile/class, zero weight, not-numbered) grouped with sample GUIDs

Enhancements

• useSelection scope switch on the query/analytics tools — operate on the current Tekla UI selection instead of the whole model ("analyze what I selected"; also faster on large models)
• assembly group key for tekla_group_weight_by and tekla_list_distinct_values

Why this release

These additions move the server from flat parts-table queries toward fabrication-oriented workflows: bill-of-materials by assembly mark, model QA sweeps that surface modeling errors, and an interactive "work on my selection" loop.

Example use cases

• "How many unique assembly marks are there, and which are the heaviest?"
• "Run modeling-issue checks and show what's missing material or not numbered."
• "I've selected some parts — sum their weight and group by profile."
• "Read VOLUME, AREA and PHASE for this GUID."
• "Export all class-20 beams as a CSV bill-of-materials."

Downloads

Asset	Use case
TeklaMcp.Server-0.2.2-net48-win-x64.zip	Production — Windows + Tekla Structures with an open model
TeklaMcp.Server-0.2.2-net8.0-mock.zip	Development / testing without Tekla

Requirements

Windows + Tekla (net48):

• Windows x64
• Tekla Structures 2023+ (validated workflow)
• Tekla running with a model open
• .NET Framework 4.8 runtime

Mock backend (net8.0):

• .NET 8 runtime

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.

v0.2.1

Tekla MCP Server v0.2.1

This patch improves tekla_select_objects for targeted, agent-friendly selection workflows.

What's new since v0.2.0

• Added guidIn parameter to tekla_select_objects (comma/semicolon/newline separated GUID list)
• Clarified that tekla_select_objects supports UDA and generic attribute filters
• Extended backend query handling (Mock + Tekla) to honor GUID allow-list filtering

Why this release

This update removes friction in scenarios where the assistant first discovers candidate elements and then needs deterministic UI selection of specific objects.

Example use cases

• Select exactly three known objects by GUID
• Select from a known GUID set and additionally filter by RU_FN1_MRK=BK1
• Repeat selection runs deterministically after analysis steps

Downloads

Asset	Use case
TeklaMcp.Server-0.2.1-net48-win-x64.zip	Production — Windows + Tekla Structures with an open model
TeklaMcp.Server-0.2.1-net8.0-mock.zip	Development / testing without Tekla

Requirements

Windows + Tekla (net48):

• Windows x64
• Tekla Structures 2023+ (validated workflow)
• Tekla running with a model open
• .NET Framework 4.8 runtime

Mock backend (net8.0):

• .NET 8 runtime

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.

v0.2.0

Tekla MCP Server v0.2.0

This release expands the MCP toolset for real-world model interrogation where the assistant needs coordinates, attribute discovery, and connection-type analytics.

Early development note: APIs and schemas may still evolve between 0.x releases.

What's new since v0.1.1

• Added tekla_find_attributes_by_value to discover candidate field names by a known value (for example, find where BK1 is stored)
• Added tekla_analyze_profile_connections to estimate unique connection/node types for a profile (beam-end proximity heuristic)
• Extended object filters with generic attribute predicates:
  • attributeName
  • attributeEquals
  • attributeContains
• Extended object payloads with coordinate/geometry context:
  • center (CenterX/Y/Z)
  • linear endpoints (StartX/Y/Z, EndX/Y/Z)
  • bounding box (MinX/Y/Z, MaxX/Y/Z)
• Mock backend now includes deterministic geometry and sample UDAs such as RU_FN1_MRK=BK1 on columns for reproducible testing

Practical scenarios now supported

• “Find all columns where base mark is BK1 even if I do not know the attribute name”
• “Show coordinates / center point for selected members”
• “Count unique connection types for profile 20P”

Downloads

Asset	Use case
TeklaMcp.Server-0.2.0-net48-win-x64.zip	Production — Windows + Tekla Structures with an open model
TeklaMcp.Server-0.2.0-net8.0-mock.zip	Development / testing without Tekla

Requirements

Windows + Tekla (net48):

• Windows x64
• Tekla Structures 2023+ (validated workflow)
• Tekla running with a model open
• .NET Framework 4.8 runtime

Mock backend (net8.0):

• .NET 8 runtime

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.

Tools included

tekla_get_connection_info, tekla_get_model_summary, tekla_list_objects, tekla_find_objects, tekla_get_object_by_guid, tekla_get_selected_objects, tekla_find_attributes_by_value, tekla_analyze_by_material, tekla_count_objects, tekla_sum_weight, tekla_group_weight_by, tekla_list_distinct_values, tekla_analyze_profile_connections, tekla_select_objects, tekla_get_object_udas, tekla_set_object_udas, tekla_set_udas_by_filter

Known limitations

• Connection analysis is a geometric heuristic (proximity to beam ends), not a strict Tekla connection object graph
• Coverage is still strongest for parts/beams/plates; broader object families remain roadmap items
• Automated tests are still limited

Full changelog

See CHANGELOG.md.

v0.1.1

Tekla MCP Server v0.1.1

Recommended release. Use this version instead of v0.1.0 — it includes complete open-source documentation, LICENSE, and README that were committed after the v0.1.0 tag.

Early development — APIs and tools may change in future versions.

What's new since v0.1.0

• MIT license and contributing guide
• English README (primary) and Russian README
• Cleaned architecture and API documentation for public GitHub audience
• CI badge and release/install instructions in README

No changes to MCP tools or server behavior — this is a documentation and open-source packaging release.

Downloads

Asset	Use case
TeklaMcp.Server-0.1.1-net48-win-x64.zip	Production — Windows + Tekla Structures with an open model
TeklaMcp.Server-0.1.1-net8.0-mock.zip	Development / testing without Tekla

Requirements

Windows + Tekla (net48):

• Windows x64
• Tekla Structures 2023+ (tested on 2023)
• Tekla running with a model open
• .NET Framework 4.8 runtime

Mock backend (net8.0):

• .NET 8 runtime

MCP client configuration

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

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

The net48 zip contains TeklaMcp.Server.exe and required DLLs — keep them in the same folder.

Tools included

tekla_get_connection_info, tekla_get_model_summary, tekla_list_objects, tekla_find_objects, tekla_get_object_by_guid, tekla_get_selected_objects, tekla_analyze_by_material, tekla_count_objects, tekla_sum_weight, tekla_group_weight_by, tekla_list_distinct_values, tekla_select_objects, tekla_get_object_udas, tekla_set_object_udas, tekla_set_udas_by_filter

Known limitations

• Object coverage focuses on parts/beams/plates; bolts, assemblies, and rebar are planned
• Tekla version compatibility beyond 2023 is not fully verified
• No automated test suite yet

Full changelog

See CHANGELOG.md.

v0.1.0

Tekla MCP Server v0.1.0

First public release. Early development — APIs and tools may change in future versions.

Highlights

• 15 MCP tools for querying, analyzing, selecting, and updating Tekla model data
• Works with Tekla Structures 2023 (Windows, live model via net48 build)
• Mock backend (net8.0) for development and testing without Tekla
• UDA writes are preview-by-default — pass apply=true to commit changes

Downloads

Asset	Use case
TeklaMcp.Server-0.1.0-net48-win-x64.zip	Production — Windows + Tekla Structures with an open model
TeklaMcp.Server-0.1.0-net8.0-mock.zip	Development / testing without Tekla

Requirements

Windows + Tekla (net48):

• Windows x64
• Tekla Structures 2023+ (tested on 2023)
• Tekla running with a model open
• .NET Framework 4.8 runtime

Mock backend (net8.0):

• .NET 8 runtime

MCP client configuration

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

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

The net48 zip contains TeklaMcp.Server.exe and required DLLs — keep them in the same folder.

Tools included

tekla_get_connection_info, tekla_get_model_summary, tekla_list_objects, tekla_find_objects, tekla_get_object_by_guid, tekla_get_selected_objects, tekla_analyze_by_material, tekla_count_objects, tekla_sum_weight, tekla_group_weight_by, tekla_list_distinct_values, tekla_select_objects, tekla_get_object_udas, tekla_set_object_udas, tekla_set_udas_by_filter

Known limitations

• Object coverage focuses on parts/beams/plates; bolts, assemblies, and rebar are planned
• Tekla version compatibility beyond 2023 is not fully verified
• No automated test suite yet

Full changelog

See CHANGELOG.md.