# Reported issues for Cernion Energy Tools MCP

Pod holds 16 of 17 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [Cernion Energy Tools MCP](/mcp/cernion-energy-tools-mcp).

## Most discussed

### Ask/Sidecar response contract for blueprint-aware read-only execution plans

## Context

OpenClaw now uses the generic Cernion Sidecar bridge instead of domain-specific Sidecar tools. The Sidecar should not know Cernion fachliche REST endpoints such as asset, MaStR, MaKo, steering, billing or other process endpoints.

The intended bridge remains the existing Sidecar-facing `cernion.ask` flow:

- OpenClaw/Sidecar calls the existing `cernion.ask` provider tool / Sidecar API path.
- Cernion resolves intent, capabilities, blueprints, guardrails and evidence internally.
- If 

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/271) · 2026-06-23 · closed · 12 comments

### Security: sichere Token-Provisionierung und Tenant/User-Bindung

# Issue 25 — Sichere Token-Provisionierung und Tenant/User-Bindung

**Bereich:** Security / Auth / Multi-Tenant · **Priorität:** Kritisch · **Ziel-Release:** v0.55

## Problem

`POST /api/tokens` kann aktuell ohne gültige Authentifizierung aufgerufen werden. Dadurch kann ein externer Client einen neuen `ck_`-Token erzeugen. Zusätzlich können neue Tokens ohne `tenantId` erstellt werden; diese Tokens sind tenant-neutral und damit nicht eindeutig auf einen Mandanten begrenzt. Eine User-Bindung exis

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/157) · 2026-05-29 · closed · 10 comments

### Discovery: OpenClaw Sidecar fuer Cernion Fach- und Prozesswissen

## Ausgangsidee

Cernion soll perspektivisch nicht nur einzelne Fachfunktionen bereitstellen, sondern als Fach- und Prozesswissensschicht fuer Stadtwerke nutzbar werden. OpenClaw, Hermes oder ein vergleichbarer Agent-Orchestrator koennte davor als Assistenz- und Uebersetzungsschicht fuer Mitarbeitende dienen: Der Mensch arbeitet in natuerlicher Sprache und rollenspezifischen Workflows, waehrend Cernion die fachlichen Begriffe, Prozesslogik, Evidenz, Guardrails und REST-faehigen Microservices lie

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/254) · 2026-06-19 · closed · 8 comments

### v0.63: Cernion Answer Dossier / Babelfish prompt architecture

## Goal

Implement **v0.63: Cernion Answer Dossier / Babelfish prompt architecture**.

Cernion should become the fachliche Orchestrierungsmaschine for energy-domain prompts. External GenAI systems such as MS365 Copilot, n8n, AnythingLLM, OpenWebUI or other agentic runtimes should not own the domain reasoning. They should only render prose from a Cernion-produced dossier.

In short:

```text
Cernion = Fachlogik, Prozesswissen, Evidence, State Machine, Guardrails, Prompt-Maschine
External renderer

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/220) · 2026-06-14 · closed · 6 comments

### Product discovery: Model Viability Management Review Workbench selector and matrix-sync panel

## Context

`origin/main` now contains both reusable source contracts for the next Stadtwerk-Mauer Workbench slice:

- `GET /api/dashboard/model-viability-evidence-gate` from #445/#450: deterministic, read-only evidence rows for one supplied operating-model candidate; no ranking, economics, legal/regulatory decision or execution.
- canonical Blueprint-Pack seed `stadtwerk-mauer-model-viability-management-review-v1` from #451/#470, including a four-row `demoProcessMatrix`, `roleLegend.M = Mitwirk

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/471) · 2026-07-22 · open · 4 comments

### Product Cut: ChatGPT Sidecar PR2 capability expansion from allowlist to full scope

## Context

Issue #388 defines the first ChatGPT Sidecar implementation slice. That first PR intentionally uses a restrictive fixed capability allowlist so the session-ticket trust boundary, TTL, revocation, tenant/user binding, draft datapoints, metering and OEO guardrail behavior can be implemented safely before broadening scope.

The first PR is now in implementation. This issue defines the **second PR product cut**: move from the initial fixed allowlist to a fuller Cernion capability scope w

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/390) · 2026-07-05 · closed · 4 comments

### VDMI Blueprint Pack: Redispatch participation readiness matrix candidate

## Context

The VDMI Blueprint & Workbench discovery loop has now closed the first Stadtwerk-Mauer Blueprint seed path:

- #301 Role Workbench Projection exists.
- #302 created the first `vdmi_blueprint_pack_seed` for `stadtwerk-mauer-pv-missing-nap-v1`.
- #303 exposed read-only Blueprint-Pack verification through `/api/operations-runbook/**`.
- #350 added the canonical `demoProcessMatrix` and Budibase matrix-sync rows for `pv-registration-missing-nap`.

The next reusable Demo-Raum / Workbench c

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/351) · 2026-06-30 · closed · 4 comments

### Enhancement: Generic Energy Sidecar MCP Connector

## Ausgangspunkt

#254 hat den Cernion Agent Sidecar MVP geliefert: kuratiertes Manifest, REST-Fassade, Policy-Gate, genau fuenf read-only/advisory Tools, Setup-Doku und DevServer-Smoke. Der naechste Schritt ist die volle Integration als MCP-/OpenClaw-faehiger Sidecar-Connector.

Thorstens Produktziel: Der Sidecar soll nicht nur ein Cernion-internes Spezialfeature bleiben, sondern als generischer Energy-Domain-Sidecar gedacht werden, der spaeter fuer OpenClaw als eigenstaendige Loesung veroeffen

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/257) · 2026-06-20 · closed · 4 comments

## Most recent

### Route Wallet Governance readiness through Capability Broker, CoPilot and Sidecar

## Context

Depends on the wallet governance preview service from the concept artifact:

`Cernion/AgentOS/10 Working Artifacts/2026-07-30-CET-Wallet-Governance-Konzept-EEG2027-FlexBG.md`

Product framing: the Corrently Wallet should act as a bilateral governance instrument between Netzanschlussnutzer and Netzbetreiber/Lieferant/MSB. CET should make that concept usable from the existing agent surfaces without allowing autonomous contract changes, market communication writes or device control.

##

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/505) · 2026-07-30 · open · 2 comments

### Wire Willi-Mako knowledge wrapper into read-only CET consumer services

## DevOps / Claude Code Handoff

### Context
Issue #494 / PR #495 added the dedicated CET wrapper service for Willi-Mako / Marktkommunikation knowledge:

- `services/willi-mako.service.js`
- Actions:
  - `willi-mako.search`
  - `willi-mako.resolveStructure`
- Internal MCP tool behind it:
  - `cernion_willi_mako_search`

This solves the base CET-internal access layer. The next step is to wire this service into selected CET consumers so MaKo knowledge can actually support validation planning, doss

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/496) · 2026-07-25 · closed · 2 comments

### Add dedicated Willi-Mako Marktkommunikation MCP wrapper service

## DevOps / Claude Code Handoff

### Context
CET already has a generic Knowledge RAG wrapper (`services/knowledge-rag.service.js`) backed by the internal Cernion MCP client (`src/mcp-client.js`) and the MCP tool `cernion_rag_search`.

For Marktkommunikation / Willi-Mako knowledge we should **not** expand the generic `knowledge-rag` service. Add a dedicated CET microservice wrapper so MaKo knowledge can be used for validation logic, structural hints, and explanation context without coupling it to

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/494) · 2026-07-24 · closed · 1 comment

### Open WebUI: document Cernion deployment profile, RBAC and safety runbook

## Kontext

The current Open WebUI README documents a local demo stack and explicitly disables auth for local testing. For any shared Cernion demo or Stadtwerk sandbox, we need a safe deployment profile that distinguishes local-only use from team/shared use.

Open WebUI supports user/global tool servers, RBAC and model/tool settings. Cernion needs a concise runbook so the integration is not accidentally exposed with local demo defaults.

## Ziel

Create/extend documentation for a Cernion Open We

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/428) · 2026-07-14 · closed · 2 comments

### Open WebUI: define draft-only Process Intake tool contract

## Kontext

Cernion separates read-only Evidence Lookup from Process Intake / Write Boundary. Open WebUI can later expose process-facing tools, but only if the server-side contract enforces tenant scope, roles, allowed operations, side-effect boundaries and HITL.

This issue is the smallest implementable slice: define and test a draft-only Process Intake tool contract for Open WebUI. It must not execute real process mutations.

## Ziel

Add a draft-only OpenAPI tool contract that accepts a user-

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/427) · 2026-07-14 · closed · 2 comments

### Open WebUI: add read-only Cernion Evidence OpenAPI tool server

## Kontext

Open WebUI can connect external services as OpenAPI tool servers. For Cernion, this is the right path for agentic tool use: Open WebUI should call an explicit read-only Evidence Lookup contract instead of embedding Cernion domain logic in a chat bridge or Workspace Tool.

## Ziel

Add a minimal external OpenAPI tool server under `integrations/open-webui/` that exposes Cernion Evidence Lookup as a read-only tool for Open WebUI Native Function Calling.

## Scope

- New server module un

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/426) · 2026-07-14 · closed · 2 comments

### Open WebUI: make Sidecar bridge configurable and session-lifecycle safe

## Kontext

Cernion has an existing Open WebUI integration in `integrations/open-webui/`. The current bridge exposes an OpenAI-compatible `/v1/chat/completions` endpoint and forwards requests to a hard-coded, expiring Sidecar session.

Open WebUI should remain an interchangeable agent frontend. Cernion Energy Tools must keep ownership of capability, blueprint, policy, evidence-router and write-boundary decisions.

## Ziel

Make the existing Open WebUI Sidecar bridge usable beyond a one-off demo 

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/425) · 2026-07-14 · closed · 0 comments

### answer-dossier: introduce slim dossier contract with answer payload density

# answer-dossier: introduce slim dossier contract with answer payload density

## Summary

Introduce a slimmer `dossierMarkdown` contract for `/api/copilot/answer-dossier` so the renderer receives a compact answer payload instead of a large governance/policy package.

Issue #238 made the answer policy evidence-first. This follow-up changes the dossier shape itself: the dossier should maximize answer-relevant facts, reasoning, and evidence per token, while keeping constraints concise and scoped t

[Read the thread](https://github.com/energychain/cernion-energy-tools/issues/242) · 2026-06-18 · closed · 3 comments

The remaining reports are on [the project's issue tracker](https://github.com/energychain/cernion-energy-tools/issues).