For energy teams running KISTERS BelVis on their own instance
Pexon builds a KISTERS BelVis API connector so Claude, ChatGPT or Copilot can read portfolio positions, schedules and time series from the customer's own BelVis system. KISTERS describes BelVis+ PFM REST APIs with OAuth2 and does not publish an endpoint list. KISTERS publishes no BelVis MCP server as of 25 October 2026.
Why BelVis is hard for agents
01 · Family
KISTERS lists BelVis EDM, PFM, WEB and archive systems, and BelVis+ modules for quotes, sales aggregation and a customer portal. The February 2026 press release says BelVis + PFM succeeds BelVis 3 PFM, eRisk and IRM. The connector is scoped to the product that is installed.
02 · Docs
Interviews from 13 November 2025 describe REST APIs with interface contracts for data retrieval and process control. They do not publish a base path or a resource list. Every backend below is confirmed against your release. The third-party belvys package is not that list.
03 · Identity
KISTERS describes OAuth2, LDAP roles per module and two-factor authentication for BelVis + PFM. A shared account would answer with the shared account's rights. The instance may be on premises or in the KISTERScloud. The connector runs in the network that can already reach it.
04 · Writes
KISTERS describes process control, migration and connections to exchanges on those REST APIs. The B2B brochure describes REST services that receive position, deal and time series data. Those operations stay off the manifest.
Checked 25 October 2026
| What we found | |
|---|---|
| Interfaces | BelVis + PFM REST APIs (REST/JSON, docs not published) · BelVis + B2B Platform REST (REST/JSON, docs not published) |
| Authentication | KISTERS says BelVis + PFM REST APIs use OAuth2, and describes LDAP-based user management with roles and rights per module and two-factor authentication. No token URL was on the pages read. How BelVis EDM authenticates was not on those pages. |
| Vendor MCP server | No vendor server. No BelVis MCP server is named on the KISTERS pages read on 25 October 2026, and a search that day did not return one from KISTERS. |
| Vendor AI assistant | None found. |
| Other connectors | The Python package belvys says it fetches portfolio time series through a BelVis REST API, and its PyPI page states it is not written or maintained by KISTERS. It is not an MCP server, and its paths were not opened. |
KISTERS AG (DE). Energy traders, municipal utilities, service providers and industrial companies. KISTERS describes BelVis + PFM for electricity and gas, names markets in Germany, Austria, Switzerland, Belgium, the Netherlands, the United Kingdom and France, and says it can run in the cloud or on premises. No BelVis-only installed-base figure was on the pages read.
What we build
Built on what KISTERS AG documents: portfolio positions, energy quantities, schedules, time series, market prices, deals. 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.
# kisters-belvis-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_portfolios: # -> portfolios this login may see
backend: confirmed in blueprint
mode: read
get_position: # portfolio -> energy quantities and position
backend: confirmed in blueprint
mode: read
list_schedules: # portfolio -> schedules and status
backend: confirmed in blueprint
mode: read
get_time_series: # portfolio, series, period -> time series values
backend: confirmed in blueprint
mode: read
get_market_prices: # instrument, period -> prices from the market price database
backend: confirmed in blueprint
mode: read
audit: every call logged with user, tool, arguments and the BelVis responseThe 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
01
REST/JSON. Documentation is not published. KISTERS describes REST APIs with interface contracts and OAuth2 for data retrieval and process control; no endpoint catalogue was public on 25 October 2026
02
REST/JSON. Documentation is not published. the B2B brochure says the platform receives position, deal and time series data via customized REST services from BelVis PFM, eRisk, IRM or another PFM system
BelVis 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.
When this is the wrong page
If the system is Schleupen.CS or Wilken ENER:GY, use that connector. BelVis holds energy data and portfolio positions on the customer's own KISTERS instance, not a billing ledger. A BelVis MCP server from KISTERS was not found on 25 October 2026; if one appears, this page is the restriction and identity work, not a second writer.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your BelVis owners and checks every backend against your release and licence. Week two tests whether a person's own BelVis 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 BelVis 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.
Not one that was named on the BelVis pages read on 25 October 2026. A search that day for a KISTERS or BelVis MCP server did not return one from KISTERS.
Portfolio positions and energy quantities, schedules and their status, time series, and market prices, on the customer's own BelVis instance. KISTERS describes those REST APIs and does not publish the paths, so each backend is confirmed in the blueprint. Process control stays off the tool list.
The call uses that person's login. KISTERS describes OAuth2, LDAP roles and rights per module, and two-factor authentication for BelVis + PFM. A shared BelVis account would answer with the shared account's rights, which is why the connector does not use one.
The two-week Readiness Blueprint is fixed at €4,900: the tool list, which BelVis product is installed, 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.
Next step
Thirty minutes with the engineer who would build the connector, with your BelVis administrator in the room if you like.