For operators reading an ENERCON wind farm

An ENERCON SCADA API and MCP server that reads wind-farm measurements on the customer's own server

Pexon builds an ENERCON SCADA API connector so Claude, ChatGPT or Copilot can read online values and stored report data from the wind farm's own SCADA server. Document D0190917-11, dated 29 April 2020, defines PDI-OPC as an OPC XML-DA server for EP1 to EP4. No ENERCON SCADA MCP server was named on enercon.de on 7 November 2026.

ENERCON SCADAbrowse_farmread_onlineread_reportAgentruns as theperson asking

Why ENERCON SCADA is hard for agents

Where a ENERCON SCADA connection needs engineering, not configuration

01 · Farm

The server is in the wind farm, and the opened description is EP1 to EP4

The 2026 SCADA Remote page puts the SCADA server on the farm fibre bus. PDI-OPC is an optional extension in document D0190917-11, dated 29 April 2020, whose title is EP1 to EP4. The 2026 technology page does not name PDI-OPC. The connector runs on the customer's network. Ardexa names TCP port 6010 as the XML server's default. The 2020 description does not state a port.

02 · Split

PDI-OPC and PDI-61400 do not carry the same history

PDI-OPC is an OPC XML-DA server and provides online data and report data. PDI-61400 uses the IEC 61400-25 model over IEC 60870-5-104:2006, is a secondary station in Monitor Direction only, and does not provide report data. The farm Ethernet bus is not the integration point: the same document says external systems are not integrated into that bus.

03 · Names

Item names come from the server, not from a public catalogue

D0190917-11 says the project structure is transmitted to the client and that the signal list sits in further documentation. That list was not opened. Ardexa's plugin warns when it meets a controller it cannot document. A tool names an OPC operation. It does not invent a tag.

04 · Writes

Setpoints exist, and they stay off the manifest

Both optional interfaces can send setpoints, and PDI-61400 can start, stop and reset a turbine. If the interface is disturbed and the server is still online, the 2020 description says the farm controller continues with the last setpoints. Online values update as often as the farm bus allows, and the shortest interval the file names is one second. Report averages are commonly one minute, ten minutes, a day, a week, a month and a year, and values of ten minutes and longer are stored on the server.

Checked 7 November 2026

ENERCON SCADA at a glance: interfaces, access and what exists for AI

What we found
InterfacesENERCON SCADA PDI-OPC (OPC XML-DA, docs public) · ENERCON SCADA PDI-61400 (IEC 60870-5-104, docs public) · ENERCON SCADA Remote (vendor client, docs public) · Farm Control Unit E2 (Modbus TCP, docs not published)
AuthenticationDocument D0190917-11 includes one licence for the SCADA server software, one for SCADA Remote, and a hardware dongle in the standard scope of a new farm. It does not describe how an OPC XML-DA client authenticates. The connector runs in the customer's network and uses the access the customer already has on the farm server.
Vendor MCP serverNo vendor server. No ENERCON SCADA MCP server is named on the SCADA Remote page or the technology page read on 7 November 2026. Public GitHub repository searches that day for an ENERCON SCADA MCP server returned no repository.
Vendor AI assistantNone found.
Other connectorsArdexa's enercon-opcxml-ardexa plugin and Teleport's installation guide both read ENERCON SCADA PDI-OPC, and Teleport also reads the Farm Control Unit E2 over Modbus TCP; neither page is an MCP server.

ENERCON GmbH (DE). Operators of ENERCON wind farms. The SCADA Remote page, read on 7 November 2026, says the SCADA server is connected to the turbines over the farm's fibre data bus. The technical description opened the same day is document D0190917-11, dated 29 April 2020, and its title covers platforms EP1 to EP4. No fleet count was on those pages.

What we build

A first ENERCON SCADA tool list, written as the manifest your IT team signs

Built on what ENERCON GmbH documents: online values, report averages, status messages, project structure. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.

# enercon-scada-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  browse_farm: # none -> the project structure the OPC server transmits
    backend: OPC XML-DA Browse on ENERCON SCADA PDI-OPC
    mode: read
  read_online: # item the server listed -> the current online value
    backend: OPC XML-DA Read of online data on PDI-OPC
    mode: read
  read_report: # item and interval -> stored averages the SCADA server kept
    backend: OPC XML-DA Read of report data on PDI-OPC
    mode: read
  read_status: # system -> main status and substatus available through SCADA Remote
    backend: OPC XML-DA Read of status messages on PDI-OPC
    mode: read
audit: every call logged with user, tool, arguments and the ENERCON SCADA response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

One interface per row

How the ENERCON SCADA interfaces differ

01

ENERCON SCADA PDI-OPC

OPC XML-DA. Documentation is public. optional server in document D0190917-11, 29 April 2020, for EP1 to EP4. OPC Foundation XML-DA V1.01. Online and report data. The signal list was not in the file, so no tag is a tool

OPC XML-DA. Docs public.

02

ENERCON SCADA PDI-61400

IEC 60870-5-104. Documentation is public. same document. IEC 61400-25 model, secondary station, Monitor Direction only. Online data. Report data is not provided. Writes stay off the manifest

IEC 60870-5-104. Docs public.

03

ENERCON SCADA Remote

vendor client. Documentation is public. the 2026 product page is a secure client for real-time and historical data. It is not an API. The 2020 description stores report copies on the remote PC as dBASE IV, and the 2026 page does not repeat that format

vendor client. Docs public.

04

Farm Control Unit E2

Modbus TCP. Documentation is not published. Teleport's guide says the FCU E2 speaks Modbus TCP. ENERCON's register list was not opened, so no register is a tool

Modbus TCP. Docs not published.

ENERCON SCADA holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.

What the connector answers, and what it will not do

Questions it answers

  • What online value does this turbine show, and when did the server last update it?
  • What ten-minute averages did the SCADA server store for this period?
  • What main status and substatus does this turbine report?

What it will not do

  • Send a setpoint, or start, stop or reset a turbine. Both optional interfaces can do that, and none of it is on the manifest.
  • Read report history from PDI-61400. The 2020 description says that interface does not provide report data.
  • Treat this as Sunny Portal, VCOM, or a login to the ENERCON Service archive. The connector reads the customer's farm server.

When this is the wrong page

If the plants are in SMA Sunny Portal or ennexOS, the SMA Monitoring connector reads them on the plant owner's consent. ENERCON SCADA reads the customer's own farm server through PDI-OPC. PDI-61400 does not provide the report history, and setpoints are not this page. An ENERCON SCADA MCP server was not named on enercon.de on 7 November 2026.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your ENERCON SCADA owners and checks every backend against your release and licence. Week two tests whether a person's own ENERCON SCADA permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.

What we need from you: a named ENERCON SCADA administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.

Sources: ENERCON SCADA Remote · ENERCON technology · Technical description D0190917-11 · Ardexa OPC XML-DA plugin · Teleport Enercon guide. Read 7 November 2026. Vendor documentation changes; verify against the current release.

Questions ENERCON SCADA teams ask before the first tool call

Does ENERCON ship an MCP server for SCADA?

Not one that was named on the SCADA Remote page or the technology page read on 7 November 2026. Public GitHub repository searches that day for an ENERCON SCADA MCP server returned no repository.

What can an assistant read from ENERCON SCADA?

Online values and stored report data from ENERCON SCADA PDI-OPC, the OPC XML-DA server in document D0190917-11 dated 29 April 2020. That description covers platforms EP1 to EP4. Report averages there are commonly one minute, ten minutes, a day, a week, a month and a year. PDI-61400 does not provide report data. The signal list was not in the file, so item names come from the server.

Where does the ENERCON SCADA connector run?

On the customer's network, against the SCADA server in that wind farm. The 2026 SCADA Remote page says the server is connected to the turbines over the farm's fibre data bus. It is not a login to ENERCON Service, and it does not send setpoints.

What does an ENERCON SCADA connector cost?

The two-week Readiness Blueprint is fixed at €4,900: the tool list, which interface the farm actually has, identity tested end to end, and a costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.

Not a sales call. An architecture call.

Thirty minutes with the engineer who would build the connector, with your ENERCON SCADA administrator in the room if you like.