MCP server for integrating WAGO PLCs with the WDx REST API
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"wago-plc-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
 [](https://hub.docker.com/r/wagoalex/wago-plc-mcp-server) [](LICENSE) [](#tool-reference) [](#demo) # wago-plc-mcp-server > MCP server that connects WAGO PLCs to LLM agents via the WDx/WDA REST API. Ask an AI assistant to read sensor values, change configuration, trigger firmware updates, or monitor entire PLC fleets - with no custom code. --- **Quick navigation:** [What it does](#new-to-wago-mcp-or-wda-start-here) · [What to ask it](#what-can-i-ask-it) · [Connecting Clients](#connecting-clients) · [Quick Start](#quick-start) · [FAQ](#frequently-asked-questions) · [Deployment Paths](#deployment-paths) · [Tool Reference](#tool-reference) · [Configuration](#configuration-reference) --- ## New to WAGO, MCP, or WDA? Start here You know PLCs - TIA Portal, Studio 5000, EcoStruxure, ladder/structured text, fieldbuses. You've never touched a WAGO controller or heard of "MCP" or "WDA." Here's the 60-second translation. **What WAGO is:** A PLC vendor, same category as Siemens/Rockwell/Schneider. Their controllers (PFC200, PFC300, Edge Controller) run a CODESYS-based runtime - your IEC 61131-3 program logic looks the same as on any other CODESYS-compatible PLC. **What WDA/WDx is:** Every WAGO controller exposes a REST API called WDA (WAGO Device Access) for **system and diagnostic management** - firmware version, network config, service health, status LEDs, reboot/firmware-update control. Think of it as the machine-readable equivalent of TIA Portal's *Online & Diagnostics* view or Studio 5000's *Controller Properties* - **not** a fieldbus, **not** OPC-UA, and **not** access to…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.