winccv8-mcp-server

WinCC V8 MCP Server

A Model Context Protocol (MCP) server that provides access to Siemens WinCC V8 SCADA systems through their REST API. Created by Andreas Vogler in 2025.

Features

🔐 Authentication

• User login with username/password credentials
• Support for Basic Authentication and Bearer Token authentication
• Automatic credential management for subsequent requests
• HTTPS support with optional certificate validation bypass

�️ Tag Management

• Connections: Read configuration data of connections and specific connection details
• Tag Groups: List all tag groups and get specific group configurations
• Structure Types: Access structure type definitions and their instances
• Tag Values: Read single or multiple tag runtime values
• Tag Writing: Write values to individual tags or batch write to multiple tags
• Tag Configuration: Access tag configuration data and list all tags with pagination

📊 Archive System

• Archives: List all process value archives and get specific archive details
• Archive Variables: Access archive variable configurations and data
• Archive Values: Read current and historical archive values with filtering
• Timers: Manage archive system timers and their configurations
• Archive Tags: Access archive system tag configurations

🌐 HTTP Transport

• Express.js server with HTTP endpoints
• Streamable HTTP server transport for MCP communication
• JSON-based request/response handling
• Error handling and proper HTTP status codes

Available Tools

Authentication

• login-user - Log in to WinCC with username and password

Tag Management

• wincc-get-connections - Read all connection configurations
• wincc-get-connection - Read specific connection configuration
• wincc-get-groups - Read all tag group configurations
• wincc-get-group - Read specific tag group configuration
• wincc-get-structure-types - Read all structure type configurations
• wincc-get-structure-type - Read specific structure type configuration
• wincc-get-structure-variables - Read structure type instances
• wincc-get-tag-value - Read runtime value of a specific tag
• wincc-get-tag-values - Read runtime values of multiple tags
• wincc-write-tag-value - Write value to a specific tag
• wincc-write-tag-values - Write values to multiple tags
• wincc-get-tag-config - Read configuration of a specific tag
• wincc-get-tags-config - Read configuration of all tags

Archive System

• wincc-get-archives - Read all process value archive configurations
• wincc-get-archive - Read specific archive configuration
• wincc-get-archive-variable - Read specific archive variable configuration
• wincc-get-archive-variables - Read all variables in an archive
• wincc-get-archive-value - Read runtime value of an archive variable
• wincc-get-archive-values - Read runtime values of multiple archive variables
• wincc-get-timers - Read all archive system timer configurations
• wincc-get-timer - Read specific timer configuration
• wincc-get-archive-tag - Read archive system tag configuration
• wincc-get-archive-tags - Read all archive system tag configurations

Installation

1. Clone this repository:

git clone https://github.com/yourusername/wincc-mcp-server.git
cd wincc-mcp-server

2. Install dependencies:

npm install

Disclaimer

Security Notice: This server has not been hardened or secured for production use. It is the responsibility of the user to implement appropriate security measures (such as authentication, authorization, network restrictions, and HTTPS) before deploying or exposing this server in any environment.

Configuration

Environment Variables

# WinCC REST API Configuration
WINCC_URL=https://localhost:34569/WinCCRestService  # Default WinCC REST service URL
WINCC_USR=username1                                # Default username
WINCC_PWD=password1                                # Default password
WINCC_BEARER_TOKEN=                                # Optional bearer token
WINCC_SKIP_CERTIFICATE_VALIDATION=false            # Set to true to skip SSL certificate validation (development only)
NODE_TLS_REJECT_UNAUTHORIZED=0                     # Set to 0 to disable TLS certificate validation (development only)

# CORS Configuration
WINCC_ALLOW_ORIGIN=*                               # CORS origin setting - '*' allows all origins, or specify specific URLs like 'http://localhost:3000'

WinCC System Setup

1. Enable WinCC REST Service: In WinCC Configuration Studio → Computer → Properties → Startup → enable the WinCC REST service
2. Configure Authentication: Set up user accounts with appropriate permissions
3. Network Configuration: Ensure the REST service port (default 34569) is accessible
4. HTTPS Certificate: For production, configure proper SSL certificates

Usage

Starting the Server

# Using npm
npm start

# Using node directly
node index.js

# Development mode with debugging
npm run dev

The server will start on port 3000 by default and listen for MCP requests at the /mcp endpoint.

Connecting with a Claude Desktop Client

To use this MCP server with the Claude AI desktop application (or other clients supporting mcp-remote), you need to configure the client to connect to this server. For the Claude Desktop application, this is typically done by editing a claude_desktop_config.json file. The location of this file varies by operating system but is usually within the Claude application's support or configuration directory.

Add or update the mcpServers section in your claude_desktop_config.json file like this:

{
  "mcpServers": {
    "WinCC V8": {
      "command": "npx",
      "args": ["mcp-remote", "http://localhost:3000/mcp"]
    }
  }
}

Technical Details

Security Considerations

• HTTPS Support: Configure HTTPS for production environments
• Certificate Validation: The server can bypass SSL certificate validation (development only)
• Authentication: Always use proper authentication credentials
• Network Security: Ensure proper firewall and network security configurations
• CORS Configuration: Use WINCC_ALLOW_ORIGIN to restrict allowed origins in production

CORS (Cross-Origin Resource Sharing)

The server includes CORS support to allow web applications to access the MCP endpoints from different origins:

• Development: Use WINCC_ALLOW_ORIGIN=* to allow all origins
• Production: Specify exact origins like WINCC_ALLOW_ORIGIN=https://yourdomain.com,https://anotherdomain.com
• Multiple Origins: Separate multiple origins with commas
• Security: Never use * in production environments with sensitive data

Troubleshooting

Common Issues

1. Connection Failed: Check WinCC REST service is running and accessible
2. Authentication Error: Verify username/password or bearer token
3. HTTPS Certificate Error: Use proper certificates or disable validation for development
4. Tag Not Found: Ensure tag names are correct and accessible
5. Permission Denied: Check user permissions in WinCC configuration

Debug Mode

Run with debugging enabled:

npm run dev

Author

Created by Andreas Vogler, 2025