01 · Docs
The Integration Layer is announced, not documented
Wilken has presented the Integration Layer but publishes no API reference for it. Which services your installation offers is the first thing the blueprint confirms with Wilken.
For utilities running Wilken ENER:GY
A Wilken ENER:GY MCP server that answers from billing and meter data under each user's own rights
A Wilken ENER:GY MCP server gives Claude, ChatGPT or Copilot named tools for contracts, meter data, bills and open market processes. Wilken is building a GY Integration Layer but publishes no API reference, so the interface is confirmed with Wilken first. Wilken ships no MCP server as of 21 September 2026; Pexon builds one.
Why Wilken ENER:GY is hard for agents
Where a Wilken ENER:GY connection needs engineering, not configuration
02 · Hosting
On-premises Java and Oracle
Many installations run on-premises on Java, Tomcat and Oracle. Reading the database directly needs Wilken's schema knowledge and a read-only grant, and it bypasses the application's own permission checks.
03 · Roadmap
ENER:GY and NTS are moving onto GY
The platform is in transition, and interfaces built today may be replaced by Integration Layer services. The connector is designed so a tool can switch its backend without changing what the assistant sees.
04 · Data
Billing and market data are regulated
ENER:GY holds billing and market communication data. Writes stay behind a person's confirmation, and no tool sends a market message.
Checked 21 September 2026
Wilken ENER:GY at a glance: interfaces, access and what exists for AI
| What we found | |
|---|---|
| Interfaces | GY Integration Layer (not published, docs not published): presented at E-world 2026 as the central connection of platform components to ENER:GY and NTS core processes; existing interfaces stay usable and are migrated gradually · WCS interface (Wilken ContentService) (not published, docs not published): standard interface for connecting document management systems to Wilken ERP and ENER:GY · ENER:GY database (database (Oracle), docs not published): the 2023 platform overview lists Oracle 11.2, 12.1 and 19c and a Java 8 / Tomcat application server for ENER:GY 4.0.16 and 4.0.17; the schema is not published |
| Authentication | Not documented publicly. Check with Wilken how the Integration Layer authenticates on your installation. |
| Vendor MCP server | No vendor server. No Wilken MCP server found; Wilken's AI work is the GY:PT assistant built into GY and ENER:GY. |
| Vendor AI assistant | GY:PT, a GPT-based assistant in GY and ENER:GY, explains process steps and regulatory requirements, with agentic automation planned for later stages (press release, 11 March 2026); Wilken also has an AI voicebot, AIVA. |
| Other connectors | epilot connects its customer portal and sales platform to Wilken, KISTERS runs Redispatch 2.0 for Wilken customers, and enaio has a document-level integration; all three are tied to their own product, none is a general agent connector. |
Wilken GmbH (Wilken Software Group) (DE). German energy and water suppliers, from municipal utilities to large suppliers such as Naturstrom, now bundled with NTS, P/5 and GY Billing on Wilken's GY solution platform.
What we build
A first Wilken ENER:GY tool list, written as the manifest your IT team signs
Wilken GmbH (Wilken Software Group) does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# wilken-energy-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
get_customer_contract: # customer ID -> contracts with tariff and status
backend: confirmed in blueprint
mode: read
get_meter_data: # metering point, period -> meter readings
backend: confirmed in blueprint
mode: read
list_bills: # customer ID -> bills with amounts and dates
backend: confirmed in blueprint
mode: read
list_open_market_processes: # metering point -> open market communication processes
backend: confirmed in blueprint
mode: read
draft_contract_note: # contract, proposed note or change -> draft for a person to confirm
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the Wilken ENER:GY responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
Wilken ENER:GY 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
- Which customers in feed-in management have missing meter data for last month?
- Show contract, meter and last bill for customer X.
- Which market communication processes for this metering point are still open?
What it will not do
- Read more than the asking user may read in ENER:GY; permissions come from Wilken, not from the connector.
- Change a contract or bill by itself: the only write tool returns a note or change that a person confirms.
- Send, answer or cancel a market communication process.
When this is the wrong page
If your clerks need process and regulatory explanations while they work in ENER:GY, GY:PT is built for that and Wilken maintains it. A connector is right when Claude, ChatGPT or Copilot has to answer from live contract, meter and billing data, or combine ENER:GY with another system.
Start with the Readiness Blueprint.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Wilken ENER:GY owners and checks every backend against your release and licence. Week two tests whether a person's own Wilken ENER:GY 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 Wilken ENER:GY 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.
Related
- Connectors for 100 source systems — the dated catalogue this page belongs to
- Claude MCP server development — how we build an MCP server for any internal system
Questions Wilken ENER:GY teams ask before the first tool call
Does Wilken ENER:GY have its own MCP server?
Not as of 21 September 2026. Wilken's AI work is GY:PT, a GPT-based assistant inside GY and ENER:GY that explains process steps and regulations. An MCP server for assistants outside ENER:GY has to be built against the interfaces Wilken provides.
Do we need extra Wilken licences or access for an AI connector?
Wilken does not publish the Integration Layer or its licence terms. Check with Wilken which interfaces your ENER:GY release includes and what they cost; the blueprint answers this before any tool is built.
Can the assistant see data a user is not allowed to see in ENER:GY?
No. The connector runs each call under the asking person's own ENER:GY rights, not a shared database account. Two users asking the same question can get two different answers, and that is tested before go-live.
What does a Wilken ENER:GY connector cost?
The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Not a sales call. An architecture call.
Thirty minutes with the engineer who would build the connector, with your Wilken ENER:GY administrator in the room if you like.