login-userLABSCO SUMMARY
The plant floor answers questions, and can be told things back.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Build from source — git clone https://github.com/mrwan84/WinCC-Unified-MCP-XT
USE CASES
01
Working out what a plant is doing right now
Read current tag values and the active alarm list together.
02
Reconstructing what happened during a shift
Query logged tag values and logged alarms over the window in question.
03
Finding the tag you actually want
Browse the configured SCADA objects instead of guessing at names.
04
Clearing an alarm board
Acknowledge alarms, and reset the ones that have been dealt with.
05
Changing a setpoint
Write the value to the tag from the same session that read it.
9 tools
Listed in project docs. Your client may show a different list.
browse-objectsget-tag-valuesget-logged-tag-valuesget-active-alarmsget-logged-alarmswrite-tag-valuesacknowledge-alarmsreset-alarmsBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/mrwan84/WinCC-Unified-MCP-XT
cd WinCC-Unified-MCP-XT
npm installEdit config.js in the project folder — set URL to your WinCC Unified GraphQL endpoint, and optionally userName and pwr for a service account.
TERMINAL
npm startAdd the mcpServers block to claude_desktop_config.json
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"WinCC Unified": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:3000/mcp"
]
}
}
}
