PLCGateway

com.plcgatewayPublished by plcgateway.comv0.1.0Updated Nov 3, 2026

Ask your plant: live PLC data, alarms, history, OEE and reports from your on-premises PLCGateway.

The publisher's own server: PLCGateway support

VerifiedSTDIODesktop onlyData & Analytics

Overview

PLCGateway's local MCP server, published by plcgateway.com; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher
plcgateway.com

Installation

In SourceWeft

  1. Open PLCGateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

PLCGateway MCP

Connect AI assistants to your plant through PLCGateway.

PLCGateway connects PLCs, CNC machines and controllers (Siemens S7, Modbus, Mitsubishi, Omron, Allen-Bradley, OPC UA and more), and every PLCGateway product has an MCP server built in. This package is a small stdio bridge: MCP clients that start servers as a command (Claude Desktop, Cursor, Cline, Windsurf, …) run it, and it forwards everything to your PLCGateway on your network.

AI client ──stdio──▶ @plcgateway/mcp ──HTTP (your network)──▶ PLCGateway on your premises ──▶ PLCs & machines
  • PLCGateway runs on your premises. The bridge talks only to the address you give it; it collects nothing and sends nothing elsewhere.
  • The assistant works with the rights of the token you give it, the same roles as people.

What you can ask

  • "How many alarms did line 3 have in the last 2 hours?"
  • "What was the filler's OEE today, and where did we lose the most time?"
  • "Summarise the last 24 hours of the tank level trend."
  • "Build a report dashboard with production and energy per shift for line 1." (draft for you to review)
  • "Add the Modbus TCP meter at 192.168.1.40 as 'Compressor 2 energy meter'." (needs the MCP configuration token)

Requirements

  • PLCGateway SCADA or Connect, reachable from the computer running the AI client, with MCP enabled
  • An API token: PLCGateway → Settings → API token (operator rights: read, write, alarm acknowledgement)
  • Node.js 18.17 or newer

For setup work (adding devices and tags) create the MCP configuration token in Settings and switch it off when done.

Setup

Claude Desktop, Cursor, Cline and other stdio clients

json
{  "mcpServers": {    "plcgateway": {      "command": "npx",      "args": ["-y", "@plcgateway/mcp"],      "env": {        "PLCGATEWAY_URL": "http://192.168.1.50:8080",        "PLCGATEWAY_TOKEN": "<your API token>"      }    }  }}

Clients that support HTTP MCP directly

You don't need this package; connect straight to PLCGateway:

json
{ "mcpServers": { "plcgateway": { "type": "http", "url": "http://192.168.1.50:8080/mcp",                                   "headers": { "Authorization": "Bearer <your API token>" } } } }

On the PLCGateway computer itself

plcgateway-scada --mcp-stdio (or plcgateway-connect --mcp-stdio) can be added as the command directly.

Configuration

VariableFlagDescription
PLCGATEWAY_URL--urlPLCGateway address, e.g. http://192.168.1.50:8080 (/mcp is added if missing)
PLCGATEWAY_TOKEN--tokenAPI token or MCP configuration token. Prefer the environment variable.
PLCGATEWAY_TIMEOUT--timeoutRequest timeout in seconds (default 120)

For HTTPS with your own certificate authority, set NODE_EXTRA_CA_CERTS=/path/to/ca.pem.

Troubleshooting

The bridge logs to stderr (visible in your client's MCP logs).

MessageWhat to check
PLCGateway not reachableAddress and port, firewall, PLCGateway running
HTTP 401/403The token (Settings → API token); a regenerated token replaces the old one
HTTP 404MCP is disabled in PLCGateway settings, or the URL points elsewhere

Links

License

The bridge in this repository is MIT licensed. PLCGateway itself is proprietary software, licensed separately.

Source: README.md at commit f613b1f

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not complete the MCP handshake.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Plcgateway integrations

PLCGateway support

com.plcgatewayOfficial publisher

Official PLCGateway support server that lets an assistant explain industrial PLC/CNC connectivity and SCADA products, check device support, quote prices and…

Streamable HTTPWeb executable
Knowledge & Memory5 toolsNov 4, 2026