Skip to content
Back to search

TIA_Portal_Openness_MCP

Drive Siemens TIA Portal V20/V21 (STEP 7, WinCC Unified) from any MCP client — create projects, generate PLC & HMI, compile & diagnose. Prebuilt runtime, no Openness coding required.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/bulaofen0036-coder/TIA_Portal_Openness_MCP with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/bulaofen0036-coder/TIA_Portal_Openness_MCP'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/bulaofen0036-coder--tia-portal-openness-mcp/badge.svg)](/listings/bulaofen0036-coder--tia-portal-openness-mcp)

HTML

<a href="/listings/bulaofen0036-coder--tia-portal-openness-mcp"><img src="/api/listings/bulaofen0036-coder--tia-portal-openness-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. **Locate the portal install root** (one of): - pass `--tia-portal-location "D:\app\TIA20\Portal V20"` when launching (recommended for non-default installs); - set the `TiaPortalLocation` user environment variable; - let it auto-read `HKLM\SOFTWARE\Siemens\Automation\_InstalledSW\TIAP{20|21}\TIA_Opns\Path`. With multiple versions installed, pass `--tia-major-version 20` (or `21`) explicitly. 2. **Mount the MCP — one command, fully automatic.** Double-click `配置MCP.bat` in the bundle root (V20: `配置MCP-v20.bat`), or run `tia.cmd config`.

> Engine exe locations by distribution: Release zip → > `tools\tiaportal-mcp\src\TiaMcpServer\bin\Release\net48\` (V21) / > `...\bin-v20\Release\net48\` (V20); git clone → `runtime\v21\` > (V20 runtime is not shipped in git — download the Release zip). > All launcher scripts resolve both layouts automatically.

It self-discovers everything: its own absolute path, the installed TIA Portal (registry) and version, and the version-matching exe (V20/V21 picked for you) — then writes the `tia-portal` entry into every AI host detected on this machine: **Claude Desktop / Claude Code / Cursor / VS Code** (existing config backed up as `.bak`, other servers preserved). Restart the AI client to load it. Options: `config --host vscode` (or `claude|claude-code|cursor`), `config --print` to copy a snippet manually. The server lists **~55 core tools of 222 by default** (~8,500 instead of ~38,800 tokens of schema per turn) so weaker models are not drowned and VS Code/Copilot's 128-tool cap and Windsurf's 100 never trip. Nothing is lost: the model reaches every other tool on demand with `FindTools("plain words")` + `CallTool(name, argumentsJson)`, and the handshake instructions tell it so. Pass `config --full` to list the whole tool surface instead. If anything fails to connect, run `tia.cmd doctor` (v2.2.8): a one-shot environment check (TIA install, exe/version match, Openness group, host registration) with the exact fix per problem; `--fix` auto-adds the Openness group. Since v2.2.7 the exe also **self-routes**: if it was built for a different TIA major version than the machine has, it transparently re-execs the matching sibling exe — grabbing the "wrong" exe no longer crashes. Manual fallback: copy the snippet from `cursor-mcp.example.json`, replace `REPLACE_ME` with this bundle's root, pick the exe path by TIA version; for non-default installs add `"--tia-portal-location","<root>","--tia-major-version","<20|21>"` to `args`. 3. **First call sequence:** `Bootstrap` → `Connect` → `OpenProject` (or `CreateProject`) → `GetProjectTree`, then read the real `PLC_*` / `HMI_RT_*` paths from the tree before continuing.

Offline validation (no TIA needed)

powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\Validate-Bundle.ps1

Checks runtime presence, blueprint file completeness, tool-count consistency, and that PLC/HMI JSON parse. Add `-Strict` for tighter manifest/matrix comparison.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 11 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "tia-portal-openness-mcp",
  3. "owner": { "name": "bulaofen", "email": "bulaofen0036@gmail.com" },
  4. "plugins": [
  5. {
  6. "name": "tia-portal-openness-mcp",
  7. "source": "./",
  8. "description": "Siemens TIA Portal Openness automation MCP — bundled V21 server + skill, one-command install."
  9. }
  10. ]
  11. }
README.md · README · 304 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # TIA Portal MCP Server (V20 + V21 · S7DCL · CLI · read-only online monitoring · one-click config · Doctor)
  2. > Current version: see the Release badge below and [CHANGELOG.md](CHANGELOG.md) (this README no longer hardcodes a version).
  3. **English** · [中文](README.zh-CN.md)
  4. > **v2.0 — the same exe is also a declarative CLI (`tia`).** Any AI emits a
  5. > YAML/JSON spec, any engineer runs one command (`tia gen spec.yaml`) — no MCP
  6. > client required. Verbs: `gen` / `patch` / `compile` / `describe` / `export` /
  7. > `import` / `prewarm` / `schema` / `version`. Exit code 0/1/2. See
  8. > `docs/CLI_quickstart.md`. The MCP server behaviour is unchanged.
  9. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) [![Release](https://img.shields.io/github/v/release/bulaofen0036-coder/TIA_Portal_Openness_MCP)](https://github.com/bulaofen0036-coder/TIA_Portal_Openness_MCP/releases) [![validate-bundle](https://github.com/bulaofen0036-coder/TIA_Portal_Openness_MCP/actions/workflows/validate.yml/badge.svg)](https://github.com/bulaofen0036-coder/TIA_Portal_Openness_MCP/actions/workflows/validate.yml)
  10. > **Free & open (MIT).** The server runs with **no license key** — there is no
  11. > license-enforcement code at all.
  12. > 🖥️ **Don't want to wire up an MCP client yourself?** Try **[TIA 助手 (TIA Assist)](https://aeenhance.com/)** —
  13. > the desktop edition built on this engine: unzip and run, built-in AI assistant, and every write to your
  14. > project waits for your approval first.
  15. > 👉 [aeenhance.com](https://aeenhance.com/) · [1-minute demo](https://aeenhance.com/#demo) · Trial: **bulaofen0036@gmail.com** · [Comparison ↓](#tia-助手-tia-assist--the-desktop-edition)
  16. ![Architecture](docs/assets/architecture.svg)
  17. Drive **Siemens TIA Portal V20 or V21** from any **MCP** client (stdio or HTTP):
  18. create projects, add hardware, generate PLC objects (Tag / UDT / DB / SCL / LAD),
  19. build **WinCC Unified** screens and events, compile-and-diagnose, and save —
  20. all through natural-language tool calls. The bundle ships **prebuilt runtimes**,
  21. a Skill spec, a static tool list, a capability matrix, PLC/HMI templates,
  22. one-shot project blueprints, and a manual. **No separate source clone required**
  23. to run.
  24. > Works with any MCP-capable client — Cursor, VS Code, Claude Desktop, or your
  25. > own HTTP client — using the same `TiaMcpServer.exe`.
  26. ## 🆕 v2.5.0 — put a TIA Portal project under Git (Version Control Interface)
  27. TIA Portal projects are binary, so Git cannot diff them — which is why "version
  28. control" in this field has long meant a pile of dated *Save As* folders.
  29. The V21 **Version Control Interface** maps a project onto an ordinary folder,
  30. **one text file per block**, so it can be diffed, committed and reviewed.
  31. This release wraps the whole round-trip into a few commands — **you never have to
  32. click anything inside the TIA Portal UI**.
  33. One sentence to your AI client is enough:
  34. ```
  35. Put the current project under Git, use D:\repos\my-plc as the workspace
  36. ```
  37. It creates the workspace → **maps the whole project automatically** (hundreds of
  38. blocks in one command, no manual ticking) → exports the text, and you `git commit`.
  39. Later, to see what changed:
  40. ```
  41. GetVersionControlStatus(changedOnly=true)
  42. → A3_4_Hoist | Unequal ← per block, not per file
  43. ```
  44. - **Covered**: FC / FB / OB / DB, PLC tag tables, UDTs — the whole software side.
  45. Hardware configuration and know-how-protected blocks are **not** covered by the
  46. VCI; the tool reports them explicitly instead of skipping them silently.
  47. - A block **must compile before it can be exported** (a TIA limitation); change
  48. *detection* is unaffected and works even on unsaved edits.
  49. - Companion `tools/vci-watch/`: after each successful compile it auto-exports,
  50. writes the CHANGELOG and runs `git commit` — the engineer does nothing.
  51. 📖 Full usage and the three behaviours you must know →
  52. **[docs/version-control-git.md](docs/version-control-git.md)**
  53. ## ⚡ Fastest start (3 steps, no coding — CLI path)
  54. > First time? **No MCP client, no code.** Once TIA is installed, these 3 steps
  55. > generate your first project in minutes.
  56. > (Wiring an AI client like Cursor / Claude Desktop over MCP instead? See
  57. > [Quick Start](#quick-start) below.)
  58. 1. **Prepare**: install **TIA Portal V20 or V21** + **.NET Framework 4.8**; add your
  59. Windows user to the local **`Siemens TIA Openness`** group and **log off/on once**
  60. (the group is not effective until re-login — the single most common blocker).
  61. **Use the exe matching your installed version** — the bundle root ships
  62. `tia.cmd` (V21) / `tia-v20.cmd` (V20); all other paths are auto-resolved.
  63. - **Health-check first**: run `tia.cmd doctor` (V20: `tia-v20.cmd doctor`) once after
  64. install — it checks TIA install / exe-version match / Openness group / host
  65. registration and prints the exact fix per problem (`--fix` auto-adds the group).
  66. 2. **Prewarm (optional, recommended)**: double-click `scripts\预热.bat` and leave the
  67. window open. It keeps one headless TIA resident so every later command connects in
  68. **~1s** (without it, each run cold-starts ~3 min). Press `Ctrl+C` to close.
  69. 3. **Generate a project**: drag a ready-made template
  70. `templates\project-blueprints\scaffold_spec_motor.json` (or
  71. `scaffold_spec_start_stop.json`) **onto `scripts\生成工程.bat`** — it creates the
  72. project → adds PLC/HMI → builds blocks → compiles → saves in one shot. Exit code
  73. `0` means success.
  74. - To customize: have any AI emit a spec per [`docs/AI_spec_prompt.md`](docs/AI_spec_prompt.md)
  75. (YAML or JSON), then drag it onto `生成工程.bat`.
  76. - CLI equivalent: add the bundle root to PATH, then `tia gen <spec>` (start with
  77. `--dry-run` for an offline check).
  78. ## TIA 助手 (TIA Assist) — the desktop edition
  79. [![TIA Assist — talk to it, it drives TIA Portal](https://aeenhance.com/img/og-cover.jpg)](https://aeenhance.com/)
  80. This repository is the **engine**: you bring your own AI client (Cursor, Claude, VS Code…) and mount it.
  81. If you'd rather **open an app and start working** — or hand it to colleagues and commissioning engineers
  82. who have never heard of MCP — the author also ships **[TIA 助手 (TIA Assist)](https://aeenhance.com/)**:
  83. the same engine inside a Windows desktop app, with the AI assistant, online monitoring and trend
  84. recording built into the UI. *(The UI and website are currently Chinese-only.)*
  85. ![TIA Assist demo: while writing an SCL block, destructive operations get their own confirmation dialog](https://aeenhance.com/video/demo-write.jpg)
  86. <sub>↑ Real screen capture (demo project): asked to write a duty/standby rotation FB for two pumps, it hit
  87. 4 compile warnings on the first build and fixed them itself down to 0 errors / 0 warnings — pausing for a
  88. human "Yes" before every write. [Watch the full recording →](https://aeenhance.com/#demo)</sub>
  89. | | Open-source MCP (this repo) | TIA 助手 (desktop edition) |
  90. |---|---|---|
  91. | Form | MCP server + `tia` CLI, driven by your own AI client | Windows desktop app, **no install — unzip and run**; V20 / V21 engines bundled and picked automatically |
  92. | AI | Bring your own (Cursor / Claude Desktop / VS Code …) | **Built-in AI assistant**; DeepSeek, Qwen, Kimi, Zhipu or any OpenAI-compatible API — or a local **Ollama** model, fully offline, project data never leaves the plant |
  93. | Write safety | Up to your client | **Every write waits for your approval**; irreversible operations (e.g. deleting blocks) are confirmed separately; hash-chained audit log |
  94. | Online values | Read-only (S7 absolute addresses / OPC UA) | **No TIA Portal needed** — symbolic read/write over S7CommPlus; writes off by default, forced read-back when enabled |
  95. | Trend recording | — | Record, overlay/split, export and replay CSV |
  96. | Environment check | `tia.cmd doctor` (CLI) | Graphical per-item check of runtimes / Openness allow-list / user group with the fix for each, one-click diagnostic bundle |
  97. | License | MIT, free | Commercial — **free trial available** |
  98. **Try it**: email **bulaofen0036@gmail.com** with your TIA Portal version (V20 / V21) and what you want to
  99. try → get the trial package, run it, send back the machine code and receive a license key.
  100. The safest first run: let it explain your own project **read-only** and check whether it got it right.
  101. More: [AI assistant](https://aeenhance.com/assistant) · [Online debugging](https://aeenhance.com/online) · [Safety boundaries](https://aeenhance.com/security) · [Manual](https://aeenhance.com/manual) · [Get started](https://aeenhance.com/start)
  102. > Both run the same engine: bugs fixed here are fixed there too, and issues reported here help both.
  103. ## Highlights
  104. - **Stability-first public generation (v0.0.39).** `PlcBuildAndImport` now returns
  105. `CapabilityDecision`, `CapabilityWarnings`, and `RecommendedNextActions`;
  106. `ApplyUnifiedHmiScreenDesignJson(strict=true)` fails when any HMI property write
  107. fails; `EnsureUnifiedHmiTag(requireVerifiedBinding=true)` requires readback as
  108. `SymbolicVerified` or `AbsoluteVerified`.
  109. - **Dual-version support (V20 + V21).** Two separate executables, not
  110. interchangeable: V21 binds the split DLLs (`Siemens.Engineering.Base/Step7/…`),
  111. V20 binds the monolithic `Siemens.Engineering.dll`.
  112. - V21 → `tools/tiaportal-mcp/src/TiaMcpServer/bin/Release/net48/TiaMcpServer.exe`
  113. - V20 → `tools/tiaportal-mcp/src/TiaMcpServer/bin-v20/Release/net48/TiaMcpServer.exe`
  114. - **Version-safe imports.** Generated Openness XML is normalized to the connected
  115. portal version on import, so a V20 portal no longer rejects blocks with
  116. *"engineering version 'V21' is not supported"*.
  117. - **S7DCL textual format.** `ExportAsDocuments` / `ExportBlocksAsDocuments` /
  118. `ImportFromDocuments` / `ImportBlocksFromDocuments` read/write the diff-friendly
  119. SIMATIC SD text format (`.s7dcl` + `.s7res`) on V20+ and are flagged *PREFERRED on
  120. V21+*. The SimaticML XML chain remains for backward compatibility.
  121. - **235 tools** across project, hardware, PLC, HMI, and online operations,
  122. layered `[L0]`/`[L1]`/`[L2]` so a normal session only needs L0 + L1.
  123. ## Requirements
  124. - Windows + **.NET Framework 4.8**
  125. - **TIA Portal V20 or V21** installed
  126. - Current user added to the **`Siemens TIA Openness`** local group (re-login after)
  127. ## Quick Start
  128. 1. **Locate the portal install root** (one of):
  129. - pass `--tia-portal-location "D:\app\TIA20\Portal V20"` when launching (recommended for non-default installs);
  130. - set the `TiaPortalLocation` user environment variable;
  131. - let it auto-read `HKLM\SOFTWARE\Siemens\Automation\_InstalledSW\TIAP{20|21}\TIA_Opns\Path`.
  132. With multiple versions installed, pass `--tia-major-version 20` (or `21`) explicitly.
  133. 2. **Mount the MCP — one command, fully automatic.**
  134. Double-click `配置MCP.bat` in the bundle root (V20: `配置MCP-v20.bat`), or run `tia.cmd config`.
  135. > Engine exe locations by distribution: Release zip →
  136. > `tools\tiaportal-mcp\src\TiaMcpServer\bin\Release\net48\` (V21) /
  137. > `...\bin-v20\Release\net48\` (V20); git clone → `runtime\v21\`
  138. > (V20 runtime is not shipped in git — download the Release zip).
  139. > All launcher scripts resolve both layouts automatically.
  140. It self-discovers everything: its own absolute path, the installed TIA Portal
  141. (registry) and version, and the version-matching exe (V20/V21 picked for you) —
  142. then writes the `tia-portal` entry into every AI host detected on this machine:
  143. **Claude Desktop / Claude Code / Cursor / VS Code** (existing config backed up
  144. as `.bak`, other servers preserved). Restart the AI client to load it.
  145. Options: `config --host vscode` (or `claude|claude-code|cursor`), `config --print`
  146. to copy a snippet manually. The server lists **65 core tools of 235 by default**
  147. (about 57 KB instead of 196 KB of tool schema per turn) so weaker models are not drowned
  148. and VS Code/Copilot's 128-tool cap and Windsurf's 100 never trip. Nothing is lost: the
  149. model reaches every other tool on demand with `FindTools("plain words")` +
  150. `CallTool(name, argumentsJson)`, and the handshake instructions tell it so. Pass
  151. `config --full` to list the whole tool surface instead.
  152. If anything fails to connect, run `tia.cmd doctor` (v2.2.8): a one-shot environment
  153. check (TIA install, exe/version match, Openness group, host registration) with the
  154. exact fix per problem; `--fix` auto-adds the Openness group. Since v2.2.7 the exe also **self-routes**: if it was
  155. built for a different TIA major version than the machine has, it transparently
  156. re-execs the matching sibling exe — grabbing the "wrong" exe no longer crashes.
  157. Manual fallback: copy the snippet from `cursor-mcp.example.json`, replace
  158. `REPLACE_ME` with this bundle's root, pick the exe path by TIA version; for
  159. non-default installs add `"--tia-portal-location","<root>","--tia-major-version","<20|21>"` to `args`.
  160. 3. **First call sequence:** `Bootstrap` → `Connect` → `OpenProject` (or
  161. `CreateProject`) → `GetProjectTree`, then read the real `PLC_*` / `HMI_RT_*`
  162. paths from the tree before continuing.
  163. ### Offline validation (no TIA needed)
  164. ```powershell
  165. powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\Validate-Bundle.ps1
  166. ```
  167. Checks runtime presence, blueprint file completeness, tool-count consistency, and
  168. that PLC/HMI JSON parse. Add `-Strict` for tighter manifest/matrix comparison.
  169. ## Build from source
  170. The full source lives under `tools/tiaportal-mcp/src/TiaMcpServer` (51 `.cs`).
  171. ```powershell
  172. # V21 (split DLLs)
  173. dotnet build tools/tiaportal-mcp/src/TiaMcpServer/TiaMcpServer.csproj -c Release
  174. # V20 (monolithic DLL) — clean intermediates first if you just built the other target
  175. dotnet build tools/tiaportal-mcp/src/TiaMcpServer/TiaMcpServer.V20.csproj -c Release
  176. ```
  177. ## Capabilities & boundaries
  178. **Can do:** projects & hardware, PROFINET, declarative PLC import, LAD XML import,
  179. WinCC Unified connections / tags (absolute addressing) / screens / button
  180. Down·Up / dynamization, compile-and-diagnose, save.
  181. **Not bundled:** Siemens install media, field projects, business-specific
  182. technology. `reference/` is style/instruction reference only. See `notBundled` in
  183. `manifest/package-manifest.json`. For what Openness **cannot** do, see
  184. `手册/openness-limitations.md`.
  185. **Read-only mode:** start the server with `--read-only` (or `TIA_MCP_READ_ONLY=1`) and every call that could
  186. change the project, the CPU or the open project is refused before it runs — listed tools, `CallTool` and the
  187. HTTP bridge alike. Reads, exports (written to — and overwriting — the path you give, never the project) and
  188. connect / open / close stay available; an older project is not upgraded on open, and an export blocked by an
  189. online PLC is not taken offline for you. The flag covers the MCP server only (CLI verbs refuse to run with it).
  190. The `lite` / `full` profile only decides which tools are listed; it is not a write protection.
  191. ## Version branches & contributing
  192. `master` is always the stable line for **TIA Portal V20 / V21**; its default
  193. behaviour never changes to accommodate older releases. Earlier TIA Portal /
  194. Openness versions live on their own branches, and contributions there are welcome:
  195. | Branch | Target version | Maintenance |
  196. |--------|----------------|-------------|
  197. | `master` | TIA Portal V20 / V21 | Official main line (day-to-day work lands here) |
  198. | `v21` | TIA Portal V21 / Openness V21 | Official; forked from master, V21-only adaptations |
  199. | `v20` | TIA Portal V20 / Openness V20 | Official; forked from master, V20-only adaptations |
  200. | `v19` | TIA Portal V19 / Openness V19 | Community |
  201. | `v18` | TIA Portal V18 / Openness V18 | Community |
  202. | `v17` | TIA Portal V17 / Openness V17 | Community |
  203. | `v16` | TIA Portal V16 / Openness V16 | Community |
  204. **How to contribute**
  205. - Send a fix or adaptation for an older release to **its own branch** (a V17 change
  206. goes to `v17`), not to `master`.
  207. - `v21` / `v20` are official lines: **anything that applies to both versions still
  208. goes to `master`.** Only use a version branch when a fix would change the other
  209. version's behaviour or depends on an API that exists in one version only — that
  210. way shared code stays in one place.
  211. - Older Openness APIs and block XML differ substantially, so branching lets each
  212. version be validated independently without destabilising main-line users.
  213. - If a fix turns out to be general and stable, a small follow-up PR back to
  214. `master` is very welcome.
  215. - Please **do not commit**: TIA project files (`.apXX`), `bin` / `obj`, logs,
  216. screenshots, backups, machine-specific absolute paths, or scratch test projects.
  217. > Want to adopt one of the version branches? Just say so in an Issue.
  218. See [CONTRIBUTING.md](CONTRIBUTING.md) for the full workflow, and
  219. [SECURITY.md](SECURITY.md) for reporting vulnerabilities.
  220. ## Documentation map
  221. | Path | What |
  222. |------|------|
  223. | `tools/tiaportal-mcp/skill/SKILL.md` | **Primary spec**: tool layers, parameter traps, Unified HMI schema, LAD/SCL boundaries |
  224. | `manifest/tools-list.json` | Static tool names/layers (runtime authority is `tools/list` after connect) |
  225. | `docs/tool-capability-matrix.md` | Capability matrix |
  226. | `docs/full-project-generation-runbook.md` | End-to-end project generation |
  227. | `docs/scl-instruction-library.md` / `docs/lad-instruction-library.md` | SCL / LAD instruction libraries |
  228. | `docs/hmi-connection-driver-matrix.md` | Communication-driver selection by CPU family |
  229. | `手册/quickstart.md` | English quick start |
  230. | `手册/TIA_NL_INTENT_RECIPES.md` | Natural-language → tool-sequence recipes |
  231. ## Standard loop (abbreviated)
  232. ```text
  233. Bootstrap → Connect → CreateProject → AddDeviceWithFallback → AddHardwareCatalogDeviceWithProbe
  234. → ConnectDeviceNodesToProfinetSubnet → GetProjectTree → ValidateAutomationContext
  235. → PlcBuildAndImport(dryRun=true per item) → PlcBuildAndImport(dryRun=false in import order)
  236. → CompileAndDiagnosePlc → EnsureUnifiedHmiConnection → EnsureUnifiedHmiTagTable → EnsureUnifiedHmiTag
  237. → EnsureUnifiedHmiScreen → ApplyUnifiedHmiScreenDesignJson → BindUnifiedHmiTagDynamization
  238. → EnsureUnifiedHmiButtonAction → SaveProject → Disconnect
  239. ```
  240. ## Contact
  241. - **Bugs / feature requests**: please open an [Issue](https://github.com/bulaofen0036-coder/TIA_Portal_Openness_MCP/issues) so others hitting the same problem can find it.
  242. - **TIA 助手 trial, custom development, partnerships**: **bulaofen0036@gmail.com**
  243. - Desktop edition: **[aeenhance.com](https://aeenhance.com/)**
  244. > Siemens, TIA Portal, SIMATIC, STEP 7 and WinCC are trademarks of Siemens AG. This project and TIA 助手 are independently developed third-party tools with no affiliation with, agency for, or authorization from Siemens AG.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.