Cernion Energy Tools MCP

Cernion Energy Tools

API-first Agentic Energy Operations Layer for Stadtwerke, DSOs and energy-service teams. Cernion combines deterministic energy-domain services, curated capability routing, evidence dossiers, VDMI role logic, HITL boundaries and read-only integration surfaces for REST, Sidecar, Microsoft Copilot, n8n, OpenWebUI and OpenClaw.

[Maintenance CI] [CodeQL] [Release] [codecov]

What This Repository Is

Cernion Energy Tools is the backend runtime behind cernion.de: a Node.js/Moleculer service platform for energy-domain automation, decision support and agentic process orchestration.

It is not just a chat frontend for energy APIs. The current platform contains:

• 138 Moleculer services in services/
• 1007 OpenAPI paths in openapi-export.json
• 304 JavaScript test files under tests/
• curated Copilot, Sidecar, OpenWebUI, n8n and OpenClaw integration surfaces that expose only governed subsets of the backend
• agentic runtime components for routing, receipts, dossiers, HITL, evidence, revalidation and observability
• durable project files with tenant-scoped ingestion, structured tables, an evidence-backed relation graph and versioned routing manifests with visible source selection; see Projektakte for APIs, provenance, limits and cleanup

Current package/OpenAPI version: 0.99.0

Public positioning

Cernion does not let the chat decide. The platform structures the objective, available data, service chain, evidence, gaps, risk and the next safe gate. The result is not a black-box answer, but a dossier-ready status or decision-readiness view for Stadtwerke, distribution-system operators and energy-service teams.

Cernion Energy Tools is not an automatic contract decision, grid-connection commitment, device-control system, MaKo execution system, billing/settlement system or tariff-mutation machine. Suitable integration scopes are ask, plan, evidence, capability lookup and read-only status. Write-like or consequential steps stay in draft, prepare or pending confirmation states and require HITL.

The public website explains Cernion as an energy-intelligence and decision platform for Stadtwerke: MaStR analysis, grid planning, §14a, Redispatch, Energy Sharing, customer-service automation and Microsoft Copilot complementarity. This repository is the deeper technical system underneath that product narrative.

Public discovery links

• Product and topic hub: Cernion Themencluster
• Capability overview: Cernion Capability Hub
• API and agent integration: MCP Tools & API and REST API
• Operational search-intent pages:
  • Verteilnetzbetreiber Software
  • Stadtwerke Prozessautomatisierung
  • §14a EnWG Nachweisakte
  • Redispatch 2.0 Bewegungsdaten
  • KI für Stadtwerke und Netzbetreiber

Why Cernion Is Agentic

Cernion is API-first, but the API is only the integration layer. The agentic part is the runtime behavior:

1. Understand an energy-domain objective Examples: validate a grid-connection scenario, build a VDMI responsibility matrix, assess BESS finance risk, identify Energy Sharing data conflicts.
2. Select a governed capability path The capability-broker maps intent to curated service chains instead of exposing the full tool catalogue to an LLM.
3. Execute deterministic microservices Energy-domain calculations and regulatory checks remain code-backed and reproducible.
4. Maintain process state Personal-agent sessions, receipts, dossiers, HITL items and object-store evidence allow work to continue beyond a single chat turn.
5. Produce auditable artifacts Outputs are not only natural-language answers; they include dossiers, evidence packages, decision frames, validation reports, receipts and traces.
6. Govern revalidation New facts can become control signals for agents: if a MaStR asset, datapoint or object-store evidence item changes, dependent decisions can be identified and rechecked.

This is the practical difference between a question-and-answer bot and an agentic energy-operations platform.

Core Architecture

External systems / humans / agents        |        vREST API, Copilot API, OpenClaw Sidecar, MCP-like tool surfaces        |        vPersonal Agent / Capability Broker / Agent Receipts / Blueprints        |        vGoverned Moleculer services        |        vDatapoints, Object Store, Knowledge RAG, Dossiers, Jobs, Observability

Runtime Layers

Main Domains

The platform covers several energy-industry work areas. The following list is representative; the OpenAPI export is the source of truth.

Agentic Components

Agentic Sitemap / AI Catalog

GET /.well-known/ai-catalog.json and GET /.well-known/ard.json publish a public catalog generated on each request from the loaded service registry and live OpenAPI metadata. Each published REST service has an entry with action/capability tokens, representative queries and an inline OpenAPI contract. The catalog also links to the full OpenAPI document and llm.txt. Root responses advertise both discovery paths through HTTP Link headers; conditional requests support ETags.

No manual JSON maintenance or LLM call is needed. Protected/private actions, service settings and runtime data are excluded. Catalog visibility grants no permission to invoke an action. See deployment details.

The formats are drafts: AI Catalog and Agentic Resource Discovery. ARD now uses ard.json; the requested ai-catalog.json remains available for clients using the predecessor path. Offline tests validate both formats against pinned upstream schemas; npm run sync:ai-catalog-schemas refreshes those fixtures from the revision pinned in the sync script (Apache-2.0).

Personal Agent

services/personal-agent.service.js is the user-facing orchestration layer. It keeps conversation state, routes intents, calls deterministic services and synthesizes results without turning the whole backend into one prompt.

Key concepts:

• layered context management ("Zwiebelmodus")
• durable execution state and resumable sessions
• file and datapoint intake
• evidence-gap handling
• work-out-loud events
• presentation-aware final artifacts

Capability Broker

services/capability-broker.service.js and src/capability-catalog.js provide curated capability routing. This is the control point that prevents agents from seeing or choosing the entire backend surface directly.

Examples of curated capabilities include:

• vdmi_role_boundary_governance
• vdmi_asset_validation_governance
• vdmi_grid_connection_decision_governance
• netzfahrplan_fnav_assessment
• znp_portfolio_assessment
• settlement_a96_reconciliation
• financier_due_diligence_assessment
• reporting_governance

Agent Receipts

services/agent-receipts.service.js turns repeatable agent workflows into versioned, testable recipes. Receipts describe matching conditions, required inputs, tool plans and knowledge plans. They are the bridge from "the agent answered" to "the platform selected a governed, inspectable workflow".

Dossiers and Decision Frames

Cernion uses dossiers and decision frames for auditable outputs. A result can include:

• facts used
• hypotheses
• evidence gaps
• risks
• forbidden assumptions
• VDMI responsibilities
• next actions
• human-review requirements

Agentic Governance and Revalidation

Two active architecture tracks are captured in GitHub issues:

• #275 Agent Governance Runtime: Bestandsanalyse vor Umsetzungsplan
• #276 Agentic Governance Layer: Faktenänderungen als Steuerungssignal für Agenten

The target direction is that a changed fact can become a control signal for agents:

MaStR / datapoint / object-store change        |        vDependency and impact analysis        |        vRevalidation queue        |        vAgent receipt / capability flow rerun        |        vAudit note, updated dossier, HITL item or exception case

This is how Cernion moves from one-time API analysis toward RPA+ for commodity energy processes: standard cases are automated, exceptions are made explicit.

Integration Surfaces

Full REST API

The complete REST API is generated from Moleculer service metadata.

• Swagger UI: GET /api/docs
• OpenAPI JSON: GET /api/openapi.json
• Static export: openapi-export.json
• Public API recipes for developer and LLM discovery: docs/public-api-recipes.md

The recipes use only synthetic examples, environment-variable based tokens and tenant-safe demo identifiers. They document consultation/read-only/pending-confirmation boundaries and are not approval, billing, tariff, device-control, contract or production-mutation demos.

Regenerate and audit:

npm run export:openapinpm run audit:openapi

Microsoft Copilot Bridge

Cernion does not expose all 600+ API paths to Microsoft Copilot. The Copilot bridge uses a curated allowlist maintained in config/copilot-operations.json.

Relevant files:

• docs/copilot-process-bridge.md
• docs/copilot-agent.json
• docs/copilot-plugin.json
• openapi-copilot.json

Generate the Copilot subset:

npm run export:openapi:copilot

The Copilot-facing surface distinguishes:

• read operations with no side effects
• draft operations that prepare suggestions
• prepare operations requiring confirmation
• consequential operations that remain blocked until explicitly governed

OpenClaw Sidecar

Cernion Energy Tools can be used from OpenClaw through the public ClawHub package @cernion/openclaw-energy-tools-sidecar. Install it in OpenClaw with:

openclaw plugins install clawhub:@cernion/openclaw-energy-tools-sidecar

The companion repository SmartEnergySolutions/cernion-openclaw-sidecar provides an OpenClaw plugin for generic Energy Sidecar providers, with Cernion as the first provider.

The product boundary is intentionally split: OpenClaw is the agent runtime for conversation, tool orchestration, memory and answer synthesis. Cernion Energy Tools is the energy-domain evidence, policy, Knowledge RAG and CET-governed process layer behind answers about MaStR assets, grid context, Redispatch, Zielnetzplanung, 14a/14d EnWG duties, process intake, Domain Router case state, Case Event Outbox/MWI and operational status.

The sidecar consumes the Cernion Sidecar contract:

• GET /api/agent-sidecar/descriptor
• GET /api/agent-sidecar/mcp/tools
• POST /api/agent-sidecar/mcp/tools/:name/call
• POST /api/knowledge-rag/query
• POST /api/evidence-router/route
• POST /api/copilot-process/intents
• GET /api/_agent/capabilities[?domain=]
• GET /api/_agent/operations[?domain=]

The boundary is deliberately strict:

• Sidecar tokens identify tenant, actor and client context; CET authorization/governance is the permission boundary.
• Domain Router and MWI tools may update internal CET PouchDB state such as case state, event delivery state and related-session links.
• evidence/hydration lookups and Blueprint plans remain read-only where that is the actual operation.
• process intake uses a separate process token and creates only pending_confirmation receipts
• admin, token, HITL-resolve and production mutation paths are blocked
• domain routing remains inside Cernion, not inside the sidecar

MCP-Style Tooling

Cernion also publishes AI-agent-friendly tool descriptions through llm.txt, capability resolution endpoints and MCP/OpenClaw-style tool lists. The public documentation page describes this as a set of ready-to-use energy tools for Stadtwerke.

Quickstart

Prerequisite: Node.js 22+

git clone https://github.com/energychain/cernion-energy-tools.gitcd cernion-energy-toolsnpm installcp .env.example .envnpm start

Default local endpoints:

• API: http://localhost:3000/api
• Swagger UI: http://localhost:3000/api/docs
• Web app: http://localhost:3000/app

Full setup guide: QUICKSTART.md

Configuration

Start with .env.example. Common variables:

LLM health:

GET /api/system/llm/health

Observability:

• GET /metrics returns Prometheus-compatible metrics
• Grafana examples: docs/observability/grafana/README.md

Auth guide: BEARER_TOKEN_AUTHENTICATION.md

Development

npm testnpm run test:unit:cinpm run test:tdd-matrixnpm run test:rest-usecasesnpm run lintnpm run audit:openapinpm run check:llmnpm run release:checknpm run release:gate

Das Runbook „Release-Gate ausführen“ beschreibt die Praxis-Evaluation mit synthetischen Mehrturn-Szenarien, Rubrik und Wiederholläufen gegen eine lokale oder HTTP-Testinstanz. release:gate ergänzt die Repository-Prüfungen um diese Abnahme.

Useful generation commands:

npm run export:openapinpm run export:openapi:copilotnpm run generate:llmnpm run blueprint:export

Create a new Moleculer service:

npm run create

Demonstrating Cernion

Good demos should show an agentic run, not only a chat answer.

Strong demo patterns:

• VDMI: generate a responsibility matrix per process step and detect role-boundary violations
• BESS: assess a site across grid connection, risks, revenue assumptions and financier evidence
• Energy Sharing: identify MaLo/MeLo, EDM and settlement conflicts that block the process
• MaStR/Revalidation: show how an external asset update can trigger rechecking of dependent decisions
• Copilot/Sidecar: show Cernion as the governed energy-domain backend behind a general-purpose agent

A useful agentic trace should make these visible:

User objective  -> intent and capability  -> selected receipt / blueprint  -> service chain  -> evidence used  -> gaps and risks  -> HITL / policy decision  -> dossier or decision artifact  -> audit trace

Documentation Map

License and Operator Context

License: GPL-3.0. See LICENSE.

Cernion is developed by STROMDAO GmbH in the context of the Cernion energy-intelligence platform.

Support and product feedback:

• GitHub Issues
• [email protected]

Workbench: verstehen, antworten, Fall im Hintergrund

Inhaltliche Nachrichten und eingefügte Fremdtexte werden über die zentrale LLM-Fassade in ein Lagebild übersetzt. CET antwortet mit relevanten Quellen und höchstens drei neuen fachlichen Rückfragen. Konkrete Arbeitsaufgaben erhalten einen Hintergrundfall; „Kein Fall“ nimmt ihn zurück. Wissens- und Statusfragen erzeugen keinen Fall. Versandwünsche führen zu einem Hinweis und auf ausdrücklichen Wunsch zu einem internen Entwurf. Quellenzuordnung und Relevanzschwelle sind in src/workbench-knowledge-sources.json konfiguriert. Details und Grenzen stehen im Tenant-Gateway-Leitfaden und im Akzeptanzbericht zu #739.

Organisationsrelevante Aussagen hält CET tenantweit fest und bestätigt sie einmal mit „Hab ich festgehalten: …“. Seltene gemeinsame Anker verbinden Aussagen verschiedener Personen; erkannte Wechselwirkungen erscheinen im Gespräch und einmal beim nächsten Kontakt der anderen Person. Tenant-Trennung und Vertraulichkeitsstufen gelten bei jedem Zugriff. Details stehen im Tenant-Gedächtnis-Leitfaden.

Tenant-Datenkatalog

Vollständige CSV-/XLSX-Texttabellen aus Open WebUI werden tenantweit als Nutzerangaben abgelegt und über dataset.query deterministisch ausgewertet. Gleicher Inhalt erzeugt auch bei erneut gesendeten Anhängen keine weitere Version oder Bestätigung. Einrichtung, Grenzen und Beispiele: Tenant-Datenkatalog. Strukturierte Nachrichten und EDIFACT: Formate, Prüfungen und Abfragen.

Originaldateien im Chat (#790)

Installation des versionierten Open-WebUI-Filters, signierte Downloads, Dateilimits und Aufbewahrung: Runbook. Ohne installierten Filter bleibt der bisherige Dokument-Textweg erhalten.

RC3 Hotfix für Mail und Dokumenteingang (#846)

Die Tabellenerkennung benötigt einen Kopf mit mindestens zwei Spalten und mindestens zwei gleich breiten Datenzeilen. WORKBENCH_DATASET_MIN_TABLE_RATIO bestimmt den erforderlichen Anteil im Tabellenblock (Standard 0.75, gültig: größer als 0.5 bis 1). Gewöhnliche Parserfehler fallen auf Text zurück; die Plausibilitätssperre für tatsächlich erkannte Tabellen bleibt aktiv. Datei-, Zeilen- und Spaltenbudgets gelten weiterhin. Nur das eindeutige, nicht verlustfrei herstellbare Open-WebUI-Zerlegungsmuster verwendet WORKBENCH_DATASET_DAMAGED.

Synthetische Fixtures regenerieren und die Regressionen lokal prüfen:

node scripts/generate-conversation-fixtures.jsnode scripts/generate-review-fixture.jsnode scripts/generate-dataset-fixtures.jsnpm test -- --runInBand tests/workbench-846.test.js tests/workbench-838.test.js

Das bestehende Live-Skript prüft zusätzlich Mailaufnahme (1), Protokollzusammenfassung (3), Mail-Verlauf neben einem fremden INVOIC-Datensatz (5) und ausdrücklich genannte Nachricht (6). Es startet einen lokalen Broker mit isolierten temporären Datenbanken und einem synthetischen Validierungs-Tenant. Alle Sprachmodellaufrufe laufen über die zentrale Fassade und das bestehende Aufruf-/Tokenbudget. Ausschließlich mit einer Nichtproduktions-Konfiguration starten:

WORKBENCH_ENV_FILE=/path/to/nonproduction.env \  WORKBENCH_VALIDATION_REPORT=/tmp/rc3-hotfix-846-live.json \  LIVE_MAX_MODEL_CALLS=80 LIVE_MAX_TOKENS=1000000 \  node scripts/validate-rc3-closeout-live.js

Die Erweiterung wurde nicht live ausgeführt. Ein Live-Bericht darf erst nach einem gesonderten Nichtproduktions-Lauf als Abnahmebeleg verwendet werden.