tia-portal-mcplisted
Install: claude install-skill Czarnak/totally-integrated-claude
# tia-portal-mcp
## Scope
Direct TIA Portal interaction via MCP tools — no code generation required.
Use MCP tools for exploration, inspection, and targeted single-step modifications.
For bulk automation, looped operations, or scripted workflows, fall back to `tia-openness-roadmap`.
---
## When MCP is the right choice
| Situation | Use |
|---|---|
| Explore project structure before writing code | MCP `browse_project_tree` |
| Read a block to understand logic or generate code | MCP `get_block_content` |
| Apply a focused, one-shot block edit | MCP `update_block_logic` |
| List tags for context or documentation | MCP `list_tag_tables` |
| Inspect hardware topology / IP addresses | MCP `read_hardware_config` |
| Find unused or unreferenced objects | MCP `read_cross_references` |
| Add a single device to the project | MCP `search_equipment_catalog` → `add_network_device` |
| Check compile errors before or after edits | MCP `compile_check` |
| Complex loops / bulk changes over many blocks | `tia-openness-roadmap` instead |
---
## Safety convention
All MCP write tools are **write-protected**. They require a preview call first, then the
write call must include both `confirm: true` and the preview response's `safetyToken`.
Never invent or reuse a token. Tokens are short-lived, single-use, and bound to the
target, requested input, project path, and current project state.
| Write tool | Required preview |
|---|---|
| `update_block_logic` | `preview_update_block_logic` |
| `cre