For energy managers running visual energy

A visual energy API and MCP server that reads stored metering-point sums on the customer's own instance

Pexon builds a visual energy API connector so Claude, ChatGPT or Copilot can read stored metering-point sums, cost centres and indicators on the customer's own instance. The version 5.3 Excel add-in page, read on 13 November 2026, says that service returns database values only. No visual energy MCP server was named on the KBR pages opened that day.

visual energyget_metering_point_sumget_metering_point_statusget_cost_centre_sumAgentruns as theperson asking

Why visual energy is hard for agents

Where a visual energy connection needs engineering, not configuration

01 · Stored

The versioned docs and the FAQ disagree on live values

The version 5.3 Excel add-in page says the service returns stored database values and does not transmit live values or device events. The 5.3.1 notes say live retrieval from the busmaster through this service is no longer supported. The undated FAQ still says the WCF service covers live and historical values. The manifest follows the versioned pages.

02 · Identity

The token is the asking user's, on that user's instance

From version 5.3 the web server is a Docker stack on Linux, with busmasters and a SQL database server, and Keycloak is the identity service. The product page also offers secureCloud. The connector runs in the customer's network and calls the customer's instance, on premises or that customer's secureCloud project. A role token is not a substitute.

03 · OPC

Live eBus values are a licence option, and the node list was not opened

The busmaster OPC server is limited to instantaneous values of connected eBus devices, DA and UA. No address space was opened, so no OPC item is a tool. The 5.3.1 notes leave the busmaster Modbus TCP server as an experiment and recommend OPC UA instead.

04 · Caps

The device cap is not one number

The busmaster page says that, depending on the licence option, up to 300 devices can be managed. The FAQ says the device count per busmaster is limited to 100 or 300 depending on the version. The blueprint reads the installed version rather than picking one cap.

Checked 13 November 2026

visual energy at a glance: interfaces, access and what exists for AI

What we found
InterfacesExcel WCF DataAccess (SOAP and REST/JSON, docs public) · Busmaster OPC DA and OPC UA (OPC DA and OPC UA, docs public) · CSV import and MSCONS (file/EDI, docs public)
AuthenticationThe Excel add-in uses an Excel/WCF access token created in the signed-in user's profile, plus the Excel URL from that profile, so the call carries that user's rights and roles. From version 5.3 the identity service is Keycloak. The 5.3.1 notes say a role token is no longer accepted for Excel/WCF access.
Vendor MCP serverNo vendor server. No visual energy MCP server is named on the KBR EnergyManagement pages read on 13 November 2026. Public GitHub repository searches that day for visual energy mcp and visual energy kbr mcp returned no repository. The MCP sentence on solutions.kbr.com is KBR Inc., a different company, and it does not name visual energy.
Vendor AI assistantNone found.
Other connectorsNone found.

KBR EnergyManagement GmbH (DE). Energy managers in industry and at companies that run visual energy on premises or in visual energy secureCloud. The product page, read on 13 November 2026, addresses a medium-sized business or an international corporation. The certificates page the same day says TÜV SÜD recertified visual energy 5 in 2025 against DIN EN ISO 50001:2018 and DIN EN 16247-1:2012, with certification until 2028. No installed-base count was on the pages opened.

What we build

A first visual energy tool list, written as the manifest your IT team signs

Built on what KBR EnergyManagement GmbH documents: metering points, stored measured values, OBIS codes, cost centres, energy uses, machines, indicators. 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.

# kbr-visual-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_metering_point_sum:    # metering point, OBIS, first and last date -> stored sum
    backend: Excel function VE4_CalcMPointSum
    mode: read
  get_metering_point_status: # metering point, OBIS, first and last date -> status string
    backend: Excel function VE4_GetMPointStatus
    mode: read
  get_cost_centre_sum:       # medium, cost centre, OBIS, period -> stored sum
    backend: Excel function VE4_CalcCCenterSum
    mode: read
  get_energy_use_sum:        # medium, energy use, OBIS, period -> stored sum
    backend: Excel function VE4_CalcEBenefitSum
    mode: read
  get_machine_sum:           # medium, machine, OBIS, period -> stored sum
    backend: Excel function VE4_CalcMSystemSum
    mode: read
  get_indicator_sum:         # indicator, OBIS, first and last date -> stored sum
    backend: Excel function VE4_CalcPIndicatorSum
    mode: read
audit: every call logged with user, tool, arguments and the visual energy 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 visual energy interfaces differ

01

Excel WCF DataAccess

SOAP and REST/JSON. Documentation is public. version 5.3.1 notes name SOAP at /Api/DataAccess.svc and WEB/REST at Api/DataAccess.svc/json, with no operation list. The documented calls are the Excel functions. The add-in page says stored database values only

SOAP and REST/JSON. Docs public.

02

Busmaster OPC DA and OPC UA

OPC DA and OPC UA. Documentation is public. a licence option. The server side is limited to instantaneous values of connected eBus devices. No node list was opened, so no OPC item is a tool

OPC DA and OPC UA. Docs public.

03

CSV import and MSCONS

file/EDI. Documentation is public. the FAQ says these sources work without a busmaster. No column layout was opened, and no file path is a tool

file/EDI. Docs public.

visual energy 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 stored sum did this metering point return for this OBIS code in this period?
  • What did this cost centre consume for this medium over this period?
  • What status string does this metering point carry for this period?

What it will not do

  • Read a live value or a device event through the Excel service. The 5.3 add-in page says those are not returned. The undated FAQ still says the WCF service covers live values, and that sentence is not a tool.
  • Use a role token. The 5.3.1 notes say a role token is no longer accepted for Excel/WCF access.
  • Change a stored value, a switching group or a schedule. The busmaster page says it synchronises switching groups and executes schedules. Those stay off the manifest.

When this is the wrong page

If the meters are in Janitza GridVis, use that connector. visual energy reads stored metering-point values on the customer's own instance. Live eBus values are the busmaster OPC option, and that node list was not opened. If the plants are in SMA Sunny Portal, the SMA Monitoring connector reads them on the plant owner's consent. No visual energy MCP server was named on the KBR EnergyManagement pages read on 13 November 2026. The MCP sentence on solutions.kbr.com is KBR Inc., a different company, and it does not name visual energy.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your visual energy owners and checks every backend against your release and licence. Week two tests whether a person's own visual energy 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 visual energy 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: Excel add-in · Excel functions · Excel login · Version 5.3.1 notes · System overview from 5.3 · Busmaster · visual energy product page · KBR certificates · KBR FAQ. Read 13 November 2026. Vendor documentation changes; verify against the current release.

Questions visual energy teams ask before the first tool call

Does KBR ship an MCP server for visual energy?

Not one that was named on the KBR EnergyManagement pages read on 13 November 2026. Public GitHub repository searches that day for visual energy mcp and visual energy kbr mcp returned no repository. The MCP sentence on solutions.kbr.com is KBR Inc., a different company, and it does not name visual energy.

What can an assistant read from visual energy?

Stored metering-point sums, a status string, cost-centre sums, energy-use sums, machine sums and indicator sums, through the documented Excel functions, on the asking user's token. The version 5.3 add-in page says live values and device events are not returned by that service.

Whose permission does the visual energy connector use?

The asking user's. The Excel login page says the add-in uses an Excel/WCF access token from that person's profile. From version 5.3 the identity service is Keycloak, and the 5.3.1 notes say a role token is no longer accepted for this access.

What does a visual energy connector cost?

The two-week Readiness Blueprint is fixed at €4,900: the tool list, the installed version, 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 visual energy administrator in the room if you like.