Developer · Local MCP server

WAGO PLC

Read and monitor WAGO PLC parameters over the WDA REST API. Read-only unless writes are allowed.

Visit WAGO PLC's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.WagoAlex/wago-plc-mcp-server
Version
2.4.4
Status
Active
Category
developer
Transport
stdio (local process)
Package
PyPI, OCI image (Docker)
Published
2026-09-21
Updated
2026-09-21
Publisher
WagoAlex (GitHub)
Website
github.com/WagoAlex/wago-plc-mcp-server
Repository
github.com/WagoAlex/wago-plc-mcp-server
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
PyPIruntime: uvxwago-plc-mcp-server2.4.4stdioTRANSPORT (required), WAGO_PLC_HOSTS (required), DEFAULT_PLC_USERNAME (required), DEFAULT_PLC_PASSWORD (required, secret), WAGO_TIMEOUT_SECONDS, WAGO_ALLOW_WRITES (required), AUDIT_LOG_FILE
OCI image (Docker)runtime: dockerdocker.io/wagoalex/wago-plc-mcp-server:2.4.4—stdioTRANSPORT (required), WAGO_PLC_HOSTS (required), DEFAULT_PLC_USERNAME (required), DEFAULT_PLC_PASSWORD (required, secret), WAGO_TIMEOUT_SECONDS, WAGO_ALLOW_WRITES (required), AUDIT_LOG_FILE

How to connect WAGO PLC

WAGO PLC runs locally from a Python package published to PyPI: wago-plc-mcp-server version 2.4.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx wago-plc-mcp-server. It reads these environment variables: TRANSPORT (required), WAGO_PLC_HOSTS (required), DEFAULT_PLC_USERNAME (required), DEFAULT_PLC_PASSWORD (required, secret), WAGO_TIMEOUT_SECONDS, WAGO_ALLOW_WRITES (required) and AUDIT_LOG_FILE; set them in the client's configuration for this server.

WAGO PLC runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/wagoalex/wago-plc-mcp-server:2.4.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e TRANSPORT -e WAGO_PLC_HOSTS -e DEFAULT_PLC_USERNAME -e DEFAULT_PLC_PASSWORD -e WAGO_TIMEOUT_SECONDS -e WAGO_ALLOW_WRITES -e AUDIT_LOG_FILE docker.io/wagoalex/wago-plc-mcp-server:2.4.4. It reads these environment variables: TRANSPORT (required), WAGO_PLC_HOSTS (required), DEFAULT_PLC_USERNAME (required), DEFAULT_PLC_PASSWORD (required, secret), WAGO_TIMEOUT_SECONDS, WAGO_ALLOW_WRITES (required) and AUDIT_LOG_FILE; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "wago-plc-mcp-server": {
      "command": "uvx",
      "args": [
        "wago-plc-mcp-server"
      ],
      "env": {
        "TRANSPORT": "<value>",
        "WAGO_PLC_HOSTS": "<value>",
        "DEFAULT_PLC_USERNAME": "<value>",
        "DEFAULT_PLC_PASSWORD": "<secret>",
        "WAGO_TIMEOUT_SECONDS": "<value>",
        "WAGO_ALLOW_WRITES": "<value>",
        "AUDIT_LOG_FILE": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 6,250 →
ServerRunsEndpoint or package
vybit.netPush notifications with personalized sounds - manage and trigger your vybits via MCP.Remote · HTTPapi.vybit.net
VynixGive AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.Remote & Local · HTTP, stdiomcp.vynix.in
W3cW3C MCP — web-standards lookup over w3c/browser-specs (GitHub, CF-reachable).Remote · HTTPgateway.pipeworx.io
Wafergraph MCPRead-only MCP server for wafergraph.com's semiconductor & AI supply-chain data: 30 tools, no auth.Remote · HTTPwafergraph-mcp.jwpalm99.workers.dev
WaitbusWorkstation-local event bus: agents wait on or emit CI/pytest/Docker/filesystem events, no polling.Local · stdioPyPI: waitbus
Wakeonlan MCP ServerWake LAN machines with Wake-on-LAN magic packets from host profiles, then confirm they came up.Local · stdio, HTTPnpm: @cyanheads/wakeonlan-mcp-server
walkerOS FlowBuild, validate, simulate, and deploy walkerOS event pipelines.Local · stdionpm: @walkeros/mcp
wallabag MCPMCP server for wallabag read-it-later entries, tags, and annotations.Local · stdioPyPI: wallabag-mcp