Wincc Unified MCP Xt MCP Server

A **Model Context Protocol (MCP)** server designed to interface with **SIEMENS WinCC Unified SCADA systems** via their **GraphQL API**. This server

Local serverstdio

What is the Wincc Unified MCP Xt MCP server?

Wincc Unified MCP Xt MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server designed to interface with SIEMENS WinCC Unified SCADA systems via their GraphQL API. This server exposes various WinCC Unified functionalities as MCP tools, enabling AI assistants and.

What the assistant can call

Once Wincc Unified MCP Xt is connected, these are the calls the assistant has available:

  • login-user — Logs in with username/password
  • browse-objects — Browses configured SCADA elements
  • get-tag-values — Retrieves live tag values
  • get-logged-tag-values — Gets historical tag data
  • get-active-alarms — Lists currently active alarms
  • get-logged-alarms — Shows previously triggered alarms
  • write-tag-values — Updates one or more tags
  • acknowledge-alarms — Acknowledges alarms
  • reset-alarms — Resets alarms

Setting it up

@modelcontextprotocol/tools on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Wincc Unified MCP Xt's toolset — login-user, browse-objects, get-tag-values and 6 more — is a fair guide to whether it matches your workflow. It is maintained by mrwan84; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Wincc Unified MCP Xt.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the wincc unified mcp xt mcp server does with a few real requests.

Available tools

ToolWhat it does
login-userLogs in with username/password.
browse-objectsBrowses configured SCADA elements.
get-tag-valuesRetrieves live tag values.
get-logged-tag-valuesGets historical tag data.
get-active-alarmsLists currently active alarms.
get-logged-alarmsShows previously triggered alarms.
write-tag-valuesUpdates one or more tags.
acknowledge-alarmsAcknowledges alarms.
reset-alarmsResets alarms.

How to install the Wincc Unified MCP Xt MCP server

{
  "mcpServers": {
    "wincc-unified-mcp-xt": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/tools"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Wincc Unified MCP Xt to login-user.
  • Use Wincc Unified MCP Xt to browse-objects.
  • Use Wincc Unified MCP Xt to get-tag-values.

Frequently asked questions

It connects Wincc Unified MCP Xt to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (login-user, browse-objects, get-tag-values, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Wincc Unified MCP Xt directly.