A GridVis MCP server that reads Janitza energy and power-quality data, never writes to a device

What we build

A first Janitza GridVis tool list, written as the manifest your IT team signs

Built on what Janitza electronics GmbH documents: projects, measuring devices, online values, historical measurement values, energy per timespan, events such as outages and threshold violations, transients, manual input values. 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.

# janitza-gridvis-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  list_devices:           # project -> measuring devices with id, name, type
    backend: GET /rest/1/projects/{pname}/devices
    mode: read
  get_energy:             # device, value type, start and end -> energy consumption
    backend: GET /rest/1/projects/{pname}/devices/{devid}/hist/energy/{value}/{type}
    mode: read
  get_live_values:        # project, devices, value types -> current online values
    backend: GET /rest/1/projects/{pname}/onlinevalues
    mode: read
  get_historical_values:  # device, value, type, timebase, range -> time series
    backend: GET /rest/1/projects/{pname}/devices/{devid}/hist/values/{value}/{type}/{timebase}
    mode: read
  get_events:             # device, range -> events such as outages and limit violations
    backend: GET /rest/1/projects/{pname}/devices/{devid}/hist/events
    mode: read
  propose_manual_reading: # manual-input device, value, timestamp -> draft entry the energy manager confirms
    backend: POST /rest/1/projects/{pname}/devices/{devid}/manualinput/{value}/{type}/{timebase}
    mode: propose
audit: every call logged with user, tool, arguments and the Janitza GridVis 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.

Checked 21 September 2026

Janitza GridVis at a glance: interfaces, access and what exists for AI

Janitza electronics GmbH (DE). Energy managers and electrical and facility teams in manufacturing plants, data centres, buildings and utilities that use Janitza UMG power analysers and GridVis for energy monitoring, power quality and ISO 50001 energy management.

Why Janitza GridVis is hard for agents

Where a Janitza GridVis connection needs engineering, not configuration

Janitza GridVis 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.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your Janitza GridVis owners and checks every backend against your release and licence. Week two tests whether a person's own Janitza GridVis 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 Janitza GridVis 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: GridVis REST API (Swagger demo) · GridVis REST API OpenAPI · GridVis REST auth and time syntax · Janipedia REST documentation · GridVis product page · GridVis Standard edition · game4automation/janitza · Official GridVis Docker image. Read 21 September 2026. Vendor documentation changes; verify against the current release.

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