Current values, logged history and the alarm list on one connection turn a WinCC Unified system into something you can interrogate — and the same server writes tags and acknowledges alarms, which is the half most read-only integrations stop before.
An MCP server that talks to WinCC Unified over its GraphQL API. Live and historical tag values, active and logged alarms, and the SCADA object tree all come through one endpoint; a service account can be configured for automatic login with token refresh.
- A login against the WinCC Unified endpoint, or an automatic service-account login with token refresh
- The configured SCADA objects browsed
- Current tag values read, and historical logged values queried
- Active alarms fetched, and logged alarms queried
- Values written back to tags
- Alarms acknowledged, and alarms reset
A current Node.js and access to a running WinCC Unified GraphQL endpoint, set as URL in config.js. A service account username and password there are optional. Writing tags and resetting alarms act on the live plant, so scope the account you configure to what the assistant should be able to change.