Is tiacommander-mcp official and is it maintained?

We found nothing naming it as a vendor’s official server. Its repository has 49 GitHub stars and its state in our directory is listed. Its last commit we recorded was on 2026-09-07.

What licence does tiacommander-mcp use?

The repository declares the NOASSERTION licence.

InfratoApp / Resources / MCP servers / tiacommander-mcp

tiacommander-mcp

tiacommander-mcp is an MCP server. Its repository has 49 GitHub stars and is licensed under NOASSERTION; we last read it on 2026-10-22.

Connects MCP-compatible AI assistants to Siemens TIA Portal using the Openness API

Install

Read from tiacommander-mcp’s own README, close to verbatim -- not written by us, and not guessed.

wget https://github.com/a4webdev/tiacommander-mcp/releases/download/v3.42.0/TiaCommander-v3.42.0-portable.zip && unzip TiaCommander-v3.42.0-portable.zip && cd TiaCommander-v3.42.0-portable && ./TiaCommander.exe

View in tiacommander-mcp’s own README ↗

What it reaches, and what it needs

Reaches

○ not recognised

Credential

○ none found

Maintenance

Stars

State

listed

Licence

NOASSERTION

From the repository

Connects any MCP-compatible AI assistant to Siemens TIA Portal via the Openness API

View on GitHub ↗2026-10-22

What tiacommander-mcp can do

29 tools documented in its README. An AI client calls these by name.

admin: Server administration, usage stats, export storage
alarm_text: Alarm texts and text lists, XLSX import / export
blocks_read: Read, inspect and export FB / FC / OB / DB blocks (XML, SCL)
delete_export: (exportId) Delete a single export.
delete_textlist: (deviceName, textlistName) Delete a user text list. System text lists rejected.
export_alarm_classes: (deviceName, outputPath) Export alarm class definitions. After export, ask the user if they want to open the file (use admin action=open_file).
export_alarm_data: (deviceName, format:csv\|xlsx; optional scope:alarm_texts\|textlists\|alarm_classes, outputPath, includeInfoText) Export alarm data to CSV or XLSX for documentation. Defaults to exports_root\alarm_tex
export_alarm_texts: (deviceName, outputPath; optional includeInfoText) Export alarm instance texts to XLSX. After export, ask the user if they want to open the file (use admin action=open_file).
export_textlists: (deviceName, outputPath; optional textListNames[]) Export text lists to XLSX. All if no filter. After export, ask the user if they want to open the file (use admin action=open_file).
get_device_profiles: All unique devices seen by the server.
get_export: (exportId; optional offset, length, raw=false) Retrieve export content with paging. raw=true returns content only, no metadata header.
get_recent_errors: (optional count=10) Last N failed tool calls with device/firmware context.
get_system_info: OS, .NET version, TIA Portal version, process uptime.
get_stats: (optional top_n=20) Call statistics per tool+action, sorted by total calls.
get_version: Server version, DB path, DB size.
list_exports: (optional tool, limit=20) Recent export results stored in export DB.
list_textlists: (deviceName) List system and user text lists with name, ID, range.
open_file: (filePath) Open a file using the Windows default application (Excel for .xlsx, browser for .html, etc.). Use after any export action to let the user inspect results immediately.
reset_device_catalog: Clear local device catalog and re-dump from TIA Portal if connected.
save_export: (exportId, outputPath) Save export content to a file. Auto-decodes base64 for binary formats (XLSX). After saving, ask the user if they want to open the file (use admin action=open_file).
search_device_catalog: (optional filter, limit=50) Search installed TIA hardware catalog from local DB. No TIA Portal needed. Use for hardware reference lookups (order numbers, CPU models, compatible modules).
update_entries: (deviceName, textlistName, entries[]) Update entries by From value. Each entry: {from, to?, text?}.
update_textlist_comment: (deviceName, textlistName, newComment) Update text list comment directly.
create_textlist: (deviceName, textlistName; optional listRange=Decimal, comment, entries[]) Create new text list. Works on empty devices (auto-seeds via template). Optionally populate with entries in one call.
add_entries: (deviceName, textlistName, entries[]) Add entries to a text list. Each entry: {from, to, text}.
delete_entries: (deviceName, textlistName, fromValues[]) Delete entries by From value.
import_alarm_classes: (deviceName, filePath) Import alarm class definitions.
import_alarm_texts: (deviceName, filePath) Import alarm instance texts from XLSX.
import_textlists: (deviceName, filePath; optional overwrite) Import text lists from XLSX.

Read from the README; names are kept only if the README contains them.

Common questions about tiacommander-mcp

What does tiacommander-mcp do?: Connects MCP-compatible AI assistants to Siemens TIA Portal using the Openness API
How do I install tiacommander-mcp?: Its own README gives this command: wget https://github.com/a4webdev/tiacommander-mcp/releases/download/v3.42.0/TiaCommander-v3.42.0-portable.zip && unzip TiaCommander-v3.42.0-portable.zip && cd TiaCommander-v3.42.0-portable && ./TiaCommander.exe. Run it where your MCP client can launch the server, and check the README for any settings it asks for.
Is tiacommander-mcp official and is it maintained?: We found nothing naming it as a vendor’s official server. Its repository has 49 GitHub stars and its state in our directory is listed. Its last commit we recorded was on 2026-09-07.
What licence does tiacommander-mcp use?: The repository declares the NOASSERTION licence.