A Qantum MCP server that answers from your plants under each user's own Qantum login

Why Qantum is hard for agents

Where a Qantum connection needs engineering, not configuration

Checked 21 September 2026

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

QOS Energy, part of Univers (formerly Envision Digital) since July 2022 (FR). Solar, wind and storage asset owners, independent power producers and O&M providers in Europe, the US and India, strong in commercial and industrial solar; at the 2022 acquisition QOS Energy monitored more than 8,000 plants totalling 10 GW in 23 countries.

What we build

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

Built on what QOS Energy, part of Univers (formerly Envision Digital) since July 2022 documents: portfolios and folders, sites and plants, inverters and solar strings, sensors and data acquisition modules, sensor measurements (raw, daily, monthly), active statuses and events, energy prices, CMMS issues. 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.

# qos-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:
  list_plants:              # portfolio or tag -> plants with site data
    backend: GET /plants
    mode: read
  get_active_alarms:        # portfolio, severity -> active statuses per plant
    backend: GET /active-statuses
    mode: read
  get_monthly_measurements: # plant, sensors, date range -> monthly values
    backend: GET /sensors/measurements/monthly
    mode: read
  list_cmms_issues:         # date range, plant -> maintenance issues
    backend: GET /cmms/issues
    mode: read
  get_energy_prices:        # plant or tag -> energy prices
    backend: GET /energy-prices
    mode: read
  draft_issue_update:       # issue ID, change -> proposed update for a person to confirm before it is sent
    backend: PATCH /cmms/issues/{id}
    mode: propose
audit: every call logged with user, tool, arguments and the Qantum 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.

Qantum 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 Qantum owners and checks every backend against your release and licence. Week two tests whether a person's own Qantum 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 Qantum 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: Postman: Qantum API v2 · Envision Digital acquires QOS Energy (2022) · Univers energy and utilities · Qantum support centre. 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