industrial-ai-siemens-mcp
Skill0 starsChanged 3 months agoMITView on GitHub
工业 AI MCP 生态分析:三层桥接模式的原理、代码、泛化验证。覆盖西门子 PLC/TIA Portal、KiCad EDA,以及通用桥接模式。
- Sends data out
In this repository219 other files it gives its agents.
- agent-doctrineSkill
- agent-evaluation-frameworkSkill
- agent-visualization-flintSkill
- hermes-agentSkill
- bailian-cliSkill
- edge-browser-automationSkill
- computer-useSkill
- jupyter-live-kernelSkill
- backup-strategiesSkill
- browser-automationSkill
- chinese-ai-free-apiSkill
- cicd-pipeline-templatesSkill
- copybaraSkill
- devops-toolkitSkill
- email-deliverabilitySkill
- monitoring-observabilitySkill
- obsidian-maintenanceSkill
- obsidian-troubleshootingSkill
- openclaw-windowsSkill
- openclaw-workerSkill
- webhook-subscriptionsSkill
- windows-dev-environmentSkill
- windows-masterSkill
- zero-downtime-deploySkill
- codebase-inspectionSkill
- github-workflowSkill
- adaptive-communicationSkill
- agent-cost-dashboardSkill
- agent-evolutionSkill
- agent-governanceSkill
- agent-osSkill
- context-efficient-toolsSkill
- context-loss-awarenessSkill
- creative-synthesisSkill
- hermes-desktop-pluginsSkill
- emotional-intelligenceSkill
- graph-engineering-workflowSkill
- hermes-maintenanceSkill
- hermes-voiceSkill
- hermes-hygieneSkill
- identity-coreSkill
- income-loopSkill
- master-synthesisSkill
- meta-cognitionSkill
- reasoning-engineSkill
- self-preservationSkill
- teaching-abilitySkill
- temporal-awarenessSkill
- hermes-themesSkill
- thinking-visualizationSkill
- user-modelingSkill
- voice-full-restoreSkill
- knowledge-graph-traversalSkill
- mcp-browser-canvasSkill
- free-api-gatewaySkill
- native-mcpSkill
- web-reverse-apiSkill
- ai-edaSkill
- huggingface-hubSkill
- industrial-ai-unifiedSkill
- The first 60 shown.
The file
Files
西门子工业 AI MCP 生态
概述
GitHub 上两个关键项目构成了西门子工业 AI 的两条腿:
- s7-mcp-bridge(TypeScript):AI Agent 通过 MCP 实时操控西门子 PLC 运行
- tia-portal-mcp(C#):AI Agent 通过 MCP 读写 TIA Portal V21 工程源码
核心模式:AI Agent → MCP 协议 → 设备 Web API / 工程 API → 工业硬件
一、s7-mcp-bridge(运行时操控)
仓库:cadugrillo/s7-mcp-bridge(20⭐,MIT)
架构
AI Agent → MCP (HTTP-Stream/stdio) → s7-mcp-bridge (Node.js)
→ HTTPS POST https://{PLC_IP}/api/jsonrpc
→ Header: X-Auth-Token
→ Body: {"jsonrpc":"2.0","method":"PlcProgram.Read","params":{"var":"\"MotorSpeed\""}}
→ 西门子 S7-1500/S7-1200 内置 Webserver关键点:PLC 自带 JSON-RPC API,本项目只是加了一层 MCP 包装。
23 个工具
- 读写:PlcProgram-Read/Write(Bool/Number/String)
- 浏览:PlcProgram-Browse(遍历标签树、DB、代码块)
- CPU控制:ReadOperatingMode / RequestChangeOperatingMode(RUN/STOP)
- 报警:Alarms-Browse / Alarms-Acknowledge
- 诊断:DiagnosticBuffer-Browse
- 备份:Plc-CreateBackup
- 工程:Project-ReadLanguages
- 认证:Api-Login/Logout/ChangePassword
通信层核心代码(Fetch.ts,仅40行)
const response = await fetch(`https://${plcIpAddress}/api/jsonrpc`, {
method: "POST",
headers: { "X-Auth-Token": authInfos.token },
body: JSON.stringify(method),
signal: AbortSignal.timeout(5000),
});注意:PLC 用自签名证书,需 NODE_TLS_REJECT_UNAUTHORIZED="0"。
配置
export PLC_IP_ADDRESSES="192.168.2.200, 192.168.2.201"
export PLC_NAMES="PLC1, PLC2"
export MCP_SERVER_PORT=57001二、tia-portal-mcp(工程开发)
仓库:Czarnak/tia-portal-mcp(20⭐,MIT,NuGet 包已发布)
配套:totally-integrated-claude — Claude Code 插件
双进程架构(最关键的设计)
TiaMcpServer (.NET 8) ← MCP stdio 宿主
↓ stdin/stdout JSON 管道
OpennessWorker (.NET Framework 4.8) ← 加载 Siemens.Engineering.* DLL
↓ TIA Portal Openness API
TIA Portal V21 实例为什么双进程:Siemens Openness API 是 .NET Framework 4.8 + Remoting API,在 .NET 8 里无法运行。通过 IPC 管道桥接。
Worker 主循环
while ((line = Console.In.ReadLine()) is not null) {
var request = JsonSerializer.Deserialize<WorkerRequest>(line);
var response = request.Method switch {
"browse_project_tree" => BrowseProjectTree(request),
"get_block_content" => GetBlockContent(request),
"update_block_logic" => UpdateBlockLogic(request),
"create_block" => CreateBlock(request),
// ... 共25个操作
};
Console.Out.WriteLine(JsonSerializer.Serialize(response));
}10 个 MCP Tool → 25 个 Worker 操作
通过 execute_read_batch / preview_write_batch / apply_write_batch 三个入口调度:
| 操作 | 能力 |
| get_block_content | 导出 PLC 块源码(Simatic ML XML + s7dcl 梯形图文本) |
| update_block_logic | 写回 AI 修改后的源码 |
| create_block / delete_block | 创建/删除 FB、FC、OB、GlobalDB |
| create_tag / update_tag / delete_tag | 管理标签表(关联 %I0.0 等硬件地址) |
| browse_project_tree | 遍历完整项目树 |
| read_hardware_config | 读硬件配置 |
| search_equipment_catalog | 搜西门子硬件目录 |
| add_network_device | 添加新 PLC/设备到项目 |
| compile_check | 编译检查 |
| start_plc / stop_plc | 远程启停 |
| create_project / archive_project | 项目管理 |
BlockExporter:AI 读 PLC 源码
// 导出 Simatic ML XML(FlgNet格式)
target.Block.Export(new FileInfo(xmlPath), ExportOptions.None);
// 同时导出 s7dcl 文档(人类可读的梯形图文本)
target.Block.ExportAsDocuments(new DirectoryInfo(tempDir), documentName);
// 返回给 AI:--- FILE: FB_Motor.xml --- ... --- FILE: FB_Motor.s7dcl --- ...BlockImporter:AI 写回源码
// 判断是 XML 还是 s7dcl 文档包
if (isXml)
target.Group.Blocks.Import(new FileInfo(xmlPath), ImportOptions.Override);
else
target.Group.Blocks.ImportFromDocuments(new DirectoryInfo(tempDir), ...);BlockMutationService:AI 从零创建 PLC 块
C# 代码动态生成 Simatic ML XML → 写临时文件 → Openness Import() → 删临时文件。支持 FB/FC/OB/GlobalDB,语言 LAD/FBD/STL/SCL/GRAPH。
写安全机制(Write Safety)
preview_write_batch → 返回 safetyToken(currentStateHash + 操作列表绑定)
↓ AI 审查预览
apply_write_batch(confirm=true, safetyToken) → 校验:
1. token 未过期(10分钟)
2. token 未被用过(一次性)
3. 项目状态未变(stateHash 匹配)
4. 操作列表未被篡改
→ 逐条执行,首失败即停
→ 写入审计日志 %LOCALAPPDATA%\TiaMcpServer\audit\安装和运行
dotnet tool install -g TiaMcpServer
tia-mcp --project C:\Projects\Line.ap21
tia-mcp doctor # 诊断环境环境要求
- Windows + TIA Portal V21 已安装
- 用户属于
Siemens TIA Openness组 - .NET 8 SDK + .NET Framework 4.8 Runtime
- TIA Portal 必须已在运行
三、可复制的通用模式
AI Agent → MCP Bridge → 设备 API/协议层 → 硬件只要设备有可编程接口(Web API、Modbus TCP、OPC-UA、MQTT),就能用同样的三层架构桥接。西门子只是最早把 Webserver 和 Openness API 做进产品的。
四、模式泛化验证:KiCad MCP Bridge(EDA 领域)
项目:kicad-mcp-bridge v1.0(自建,D:/Hermes/kicad-mcp-bridge/,27 工具)
将三层桥接模式应用到电子设计自动化(EDA)领域,验证了该模式的通用性:
AI Agent → MCP Server (Python stdio) → pcbnew + sexpr → KiCad 工程文件(原理图 + PCB + Gerber)与西门子项目的对比
| 维度 | s7-mcp-bridge | tia-portal-mcp | kicad-mcp-bridge |
| 目标 | S7-1500 PLC | TIA Portal V21 | KiCad 完整 EDA |
| API 层 | JSON-RPC Webserver | Openness .NET | pcbnew + sexpr |
| MCP 层 | Node.js | C# stdio | Python stdio |
| 工具数 | 23 | 10→25 | 27 |
| 操作对象 | 运行时标签 | 工程源码 | 原理图→PCB→Gerber→BOM |
kicad-mcp-bridge 已升级到 v1.0(2026-07-23),新增原理图操作、制造出片(Gerber/钻孔/BOM/3D STEP)、差分对布线、批量放置。是三个项目中工具数最多的。
关键发现
- Python 是 MCP bridge 的最佳语言:嵌入式/工控领域大量工具已有 Python API(KiCad pcbnew、pyModbus、opcua-asyncio),直接用 Python 写 MCP server 零语言切换成本
- stdio 模式比 HTTP 更适合本地工具:无需端口管理,无网络暴露风险,Hermes 直接 fork 子进程即可
- 嵌入式背景是护城河:写 PLC bridge 需要懂梯形图,写 PCB bridge 需要懂电路约束——纯软件工程师跨不过这道门槛
详见 [[kicad-mcp-bridge]] 技能(v1.0,27 工具)。
五、相关生态项目
| 项目 | 说明 |
| NX_MCP (DreamEnding) | MCP 操控西门子 NX CAD,47+ 工具 |
| nxopen-mcp | 给 AI 注入 NXOpen .NET API 知识库 |
| FaultMind | Agentic RAG 做 PLC/SCADA 根因分析 |
| tia-git-addin | TIA Portal V21 Git 插件(同作者) |
| AI-PLC (miyatti777) | 4 阶段 AI 产品生命周期流水线 |
| edge-agents (ForestHubAI) | 30MB 边缘 AI Agent 运行时,GPIO/UART/MQTT |
| kicad-mcp-bridge v1.0 | 27 工具,完整 EDA 流水线:原理图→PCB→Gerber→BOM。三个项目中工具最多。 |
六、对开发者的机会
- Python + AI Agent 经验 → 写 MCP Bridge 连接各类工控协议
- 嵌入式背景 → TinyML/边缘推理是纯软件人不具备的护城河
- MCP 协议已成为 AI 进入工控的标准桥接层,先发优势明显
- 该交叉领域目前几乎空白,商业价值极高
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

