LabscoMCP early access ↗
heilingbrunnerMCP SERVER

TIA-Portal MCP-Server

Drive a Siemens TIA Portal project from GitHub Copilot chat — open it, read its structure, export blocks, compile PLC software.

by heilingbrunner ↗IoT, Smart Home & Embedded HardwareCommunity

LABSCO SUMMARY

Automation work that normally means clicking through TIA Portal, driven from chat instead.

The natural shape is a chained instruction — connect, open the project, export or compile, close, disconnect — and the project's own examples read exactly like that. Two prerequisites bite people before anything works: the TiaPortalLocation variable and Openness group membership are both Windows-side setup that TIA Portal will not prompt you about.

What it is

A Visual Studio Code extension that registers an MCP server for Siemens TIA Portal V20. It connects to a running TIA Portal instance through Siemens Openness, so an agent in Copilot chat can work with the project directly.

What you get

  • Connect to a running TIA Portal instance and open a project file
  • Read back the project structure, including as markdown you can paste into documentation
  • Export all blocks from a PLC software target to a folder in your workspace
  • Export all types from the same PLC software target
  • Compile a named PLC software target
  • Close the project and disconnect when the session is done

Requirements

Windows with Siemens TIA Portal V20 installed and running, Siemens.Openness, and .NET Framework 4.8. The TiaPortalLocation user environment variable must point at the Portal V20 install directory, and your Windows account must be in the Siemens TIA Openness group. In VS Code you need GitHub Copilot with MCP enabled; the extension writes the server entry for you via its “TIA Portal: Add MCP Server Configuration” command.

Setup effort

Add the configuration to your client