Skip to main content
Glama
TIA Portal MCP Server

TIA Portal MCP Server

by BJM1122

Related Servers

Alternatives to TIA Portal MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that connects AI assistants to Siemens TIA Portal via the Openness API. AI-assisted PLC programming, project management, hardware configuration, cross-reference analysis, and deployment. 19 tools, 230 actions.
      60
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for controlling Siemens TIA Portal, enabling AI agents to connect, read PLC tags, list blocks, inspect project structure, and compile projects. This community edition provides 5 read-only tools under the MIT license.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to inspect and modify Siemens PLC projects through the Openness API: browsing block trees, reading and generating ladder logic, creating data blocks and SCL source, importing/exporting, compiling, editing tag tables, and launching, opening, saving, or archiving projects. Changes stay in memory until an explicit save, and write tools refuse to overwrite existing blocks unless told to.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP bridge for Siemens TIA Portal that enables AI assistants to inspect PLC projects, import/export programs, and compile with read-only defaults and opt-in writes.
      -

    TDQS

    B3.2/5.0

    Scored across 47 tools

    Disambiguation3/5

    Descriptions are unusually detailed and often explicitly carve out boundaries, but there are several clusters with overlapping purpose: tia_export_hmi_bundle / tia_export_hmi_native / tia_export_hmi_configuration, tia_edit_hmi_text / tia_update_hmi_object / tia_edit_hmi_native, and tia_search_export / tia_fast_lookup / tia_trace_symbol / tia_trace_data_flow all read from the same export index. The classic-versus-Unified HMI split and the plan/apply pairing add further near-duplicates (e.g. tia_create_hmi_project_plan vs tia_create_unified_hmi_project_plan, tia_apply_hmi_project vs tia_apply_unified_hmi_project) that an agent must carefully disambiguate by target type.

    Naming Consistency4/5

    Almost everything is snake_case with a tia_ prefix and a verb_noun shape (tia_create_import_plan, tia_apply_import, tia_search_export, tia_trace_symbol). Deviations are minor: noun-phrase names like tia_doctor and tia_hmi_authoring_capabilities, the adjective-first tia_fast_lookup, and one tool (plc_probe_ports) outside the tia_ prefix.

    Tool Count2/5

    47 tools is far beyond a comfortably scoped surface, and the count is inflated by parallel classic/Unified HMI variants and three-stage plan/apply pipelines. Many tools are legitimate, but the set is large enough that discovery and selection become a burden rather than an aid.

    Completeness3/5

    The domain surface is broad: session preparation, live queries, export indexing, symbol/data-flow tracing, block import with rollback, and HMI inspect/plan/apply/export for both classic and Unified. However, there are notable gaps—no object deletion, no PLC download or online monitoring, no alarm or recipe authoring, and PLC program creation is limited to importing pre-authored Simatic ML candidates.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues