IndustriConnect PROFINET MCP
PROFINET DCP discovery and GSDML parsing. Cyclic I/O in the public server goes through a mock.
Who it's for
An engineer attaching an MCP client to PROFINET. Treat the write policy as the safety boundary: a gated write is still a write once you arm it.
Caveat / limitations
Discovery, naming, and IP assignment need raw sockets and are described as not yet tested on hardware. Cyclic I/O is documented only through a mock, or through a pre-commissioned Hilscher cifX card on Linux. Set PROFINET_BACKEND=mock for the JSON device. For a production line, use the PLC vendor's engineering tool or OPC UA.
Protocols
Sources
- Repositoryhttps://github.com/IndustriAgents/PROFINET-MCP
- IndustriAgentshttps://industriagents.com/connect
This page: https://otaihub.com/tools/industri-connect-profinet
Same category
- CODESYS Development System MCP ServerOfficial CODESYS add-on that lets an MCP client read and write the open project, compile, and fix Structured Text.
- IndustriConnect Modbus MCPOpen-source Modbus TCP, UDP, and RTU client for MCP hosts, with a mock device and writes off by default.
- IndustriConnect OPC UA MCPPython and Node OPC UA MCP servers with the same tools: browse, read, history, alarms, and gated writes.
- IndustriConnect MQTT / Sparkplug MCPMQTT client that publishes, subscribes, and decodes Sparkplug B instead of handing the model raw bytes.