Ask your plant: live PLC data, alarms, history, OEE and reports from your on-premises PLCGateway.
Connect Runs on your machine
claude mcp add plcgateway -e PLCGATEWAY_URL=<PLCGATEWAY_URL> -e PLCGATEWAY_TOKEN=<PLCGATEWAY_TOKEN> -- npx -y @plcgateway/[email protected]{
"mcpServers": {
"plcgateway": {
"command": "npx",
"args": [
"-y",
"@plcgateway/[email protected]"
],
"env": {
"PLCGATEWAY_URL": "<PLCGATEWAY_URL>",
"PLCGATEWAY_TOKEN": "<PLCGATEWAY_TOKEN>"
}
}
}
}{
"mcpServers": {
"plcgateway": {
"command": "npx",
"args": [
"-y",
"@plcgateway/[email protected]"
],
"env": {
"PLCGATEWAY_URL": "<PLCGATEWAY_URL>",
"PLCGATEWAY_TOKEN": "<PLCGATEWAY_TOKEN>"
}
}
}
}{
"servers": {
"plcgateway": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@plcgateway/[email protected]"
],
"env": {
"PLCGATEWAY_URL": "<PLCGATEWAY_URL>",
"PLCGATEWAY_TOKEN": "<PLCGATEWAY_TOKEN>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
PLCGATEWAY_URLRequired | Address of your PLCGateway SCADA or Connect, e.g. http://192.168.1.50:8080 |
PLCGATEWAY_TOKENRequired, secret | API token (PLCGateway → Settings → API token), or the MCP configuration token for device/tag setup |
Details
| Package | @plcgateway/[email protected] (NPM, stdio) |
| First published | 13 Nov 2026 |
| Last updated | 13 Nov 2026 |
| Registry name | com.plcgateway/plcgateway |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.