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_valueto discover candidate field names by a known value (for example, find whereBK1is stored) - Added
tekla_analyze_profile_connectionsto estimate unique connection/node types for a profile (beam-end proximity heuristic) - Extended object filters with generic attribute predicates:
attributeNameattributeEqualsattributeContains
- 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)
- center (
- Mock backend now includes deterministic geometry and sample UDAs such as
RU_FN1_MRK=BK1on 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):
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.