MCP server for Siemens TIA Portal automation engineering, providing tools for project lifecycle management, batch operations on blocks and tags, and network hardware configuration
TiA Portal MCP has 14 tools with mixed definition quality. Strengths: most tools have descriptions and some parameter schemas are present. Weaknesses: descriptions are often generic or too brief (many under 100 chars, well below the 194-char baseline); parameter schemas lack type information in many cases; output schemas are entirely undocumented; error handling is absent; no tool annotations (readOnlyHint/destructiveHint); no guidance on recovery or next steps. The batch/network tool abstractions are reasonable for composition, but individual tool quality is below production baseline. The server demonstrates engineering discipline (tests verify description completeness) but falls short on LLM-facing usability.
Apply a batch of write operations after preview confirmation. Requires confirm=true and a valid safety token from preview_write_batch. No batch-wide rollback is performed. Never saves the project or compiles it—use save_project and compile_check separately.
Archive a TIA Portal project. Requires confirm=true to execute
Browse the structure of a TIA Portal project, including blocks, tags, types, and other project elements
Close the currently open TIA Portal project. Requires confirm=true to execute
Perform a compile check on a TIA Portal project or specific block, without saving the project
Create a new TIA Portal project. Requires confirm=true to execute
Output schemas are completely undocumented. No tool declares what it returns, preventing LLMs from planning downstream calls or extracting relevant data. Required by pattern:tool and pattern:response-shaper.
Parameter schemas lack type information. Properties like 'operationId', 'operation', 'blockPath', etc. are declared as objects with nested properties, but root-level parameter types (string, integer, boolean, object) are missing from many tool inputs. This violates JSON Schema best practices and prevents LLM understanding of what type of value to pass.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2025-06-18+ | v2 |
Execute a batch of read-only operations on the TIA Portal project. Supports operations such as: get_block_content, get_tag_table, list_tags, read_cross_references, and others.
Get the current status of the TIA Portal project, including project path, open/closed state, and other metadata
Read network hardware configuration from the TIA Portal project. Supports operations like read_hardware_config and search_equipment_catalog. Results are paginated; pageSize parameter controls result count (1..200, defaults to 50). Hardware data is returned in a specific order: devices first, then subnets. The cursor value must remain unchanged between requests.
Write network hardware configuration to the TIA Portal project. Supports operations like add_network_device, configure_network_device, create_subnet, update_subnet, and delete_subnet. Connected subnet deletion is allowed. Does not delete any device (root device count does not change; nested device user group members are outside that count, and device user groups remain unaffected). No batch-wide rollback is performed. Never saves the project or compiles it—use save_project and compile_check separately.
Open a TIA Portal project. Requires confirm=true to execute after preview
Preview a batch of write operations without applying them. Returns a safety token that must be used to confirm and apply the changes. Supports operations such as: create_tag, delete_tag, update_tag, create_block, delete_block, update_block_logic, create_user_constant, delete_user_constant, update_user_constant, update_type_content, and others. No batch-wide rollback is performed. Safety token lifetime is 5 minutes.
Save the currently open TIA Portal project. Requires confirm=true to execute
Save the currently open TIA Portal project with a new name or location. Requires confirm=true to execute. Rebind parameter controls whether to open the copied project after save
Descriptions are too brief for LLM decision-making. Baseline is 194 chars; most tools are under 100 chars. 'Get the current status of the TIA Portal project...' (47 chars) lacks context for selection. Should include: WHAT does it do, WHEN to call it, WHAT prerequisite state is needed.
No tool annotations present. Destructive tools (apply_write_batch, delete_* operations in batch, archive_project, close_project) lack destructiveHint. Read-only tools lack readOnlyHint. Idempotent operations lack idempotentHint. These are essential for agent planning and safety.
Error handling guidance is absent. No tool describes what to do on failure. LLMs receive no recovery paths, classification (retryable vs fatal), or actionable next steps. 'Token expired' should suggest 'Call preview_* again'; 'Project not found' should offer alternatives.
Batch operations lack documented limits and pagination guidance. execute_read_batch and preview_write_batch accept unbounded 'operations' arrays. No mention of maximum batch size, expected latency, or what happens if the batch is huge. LLMs may pass 1000s of operations causing timeouts.
Parameter dependencies and constraints are underdocumented. 'confirm' and 'safetyToken' are required together for write operations, but this mutual dependency is not stated. 'operation' in batch requests requires specific other fields (blockPath for block operations, tableName for tag operations), but which field goes with which operation is unclear from parameter descriptions.
No input validation rules stated. Parameters like 'projectPath' lack guidance on format (file path? directory? URL?). 'pageSize' in network_read has a constraint '1..200' in description, but many other numeric parameters lack min/max. LLMs will guess and pass invalid values.