For energy suppliers and grid operators running SOPTIM

A SOPTIM MCP server that answers balancing and schedule questions under each user's own rights

A SOPTIM MCP server gives Claude, ChatGPT or Copilot named tools for shadow balances, schedule status, clearing items and portfolio positions. SOPTIM keeps an API documentation for its Elements platform that is not public. SOPTIM ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.

Why SOPTIM is hard for agents

Where a SOPTIM connection needs engineering, not configuration

01 · Docs

API documentation exists but is closed

SOPTIM maintains a central API documentation with live testing, but it is not public. Access comes with a customer or project relationship, so the blueprint starts from your copy of it.

02 · Versions

VIM, PMS and Elements coexist

Installed bases still run the older VIM and PMS products next to the newer Elements editions. The API surface differs between legacy on-premises and Elements SaaS, and the tool list follows what you run.

03 · Deadlines

Schedules and MaBiS are regulated processes

Schedule submissions and MaBiS clearing run on regulatory deadlines. An agent reads their status and drafts at most; it never sends a schedule or a clearing response.

04 · Volume

Quarter-hour values across balancing groups

Time series at quarter-hour resolution across many balancing groups are too large to pass to a model. Tools aggregate on the server before answering.

Checked 21 September 2026

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

	What we found
Interfaces	SOPTIM Elements platform APIs (API, type not published, docs behind customer or partner login): SOPTIM keeps a central API documentation for the Elements platform with live endpoint testing; no public URL, access appears to be customer-only · ELEMENT:DataHub (integration layer, docs not published): maps Excel, XML, CSV, REST or SOAP sources, triggered by time, event, API call or file drop (S3, SFTP) · AS4 and TSO communication (file/EDI, docs public): EDIFACT and ESS schedules with transmission system operators and market partners; public market standards
Authentication	Not documented publicly. Check with SOPTIM how API access is granted for your Elements tenant or on-premises installation.
Vendor MCP server	No vendor server. No SOPTIM MCP server found.
Vendor AI assistant	The subsidiary esterion GmbH provides AI-based forecasts, load profile analyses and price calculations; no assistant inside the Elements product found.
Other connectors	None found.

SOPTIM AG (DE). German energy suppliers, balancing group managers and distribution and transmission system operators using SOPTIM Elements, and the older SOPTIM VIM and PMS, for sales, portfolio, balancing group and schedule management.

What we build

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

SOPTIM AG does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.

# soptim-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_shadow_balance:       # balancing group, month -> shadow balance against the MaBiS summary with deviations
    backend: confirmed in blueprint
    mode: read
  list_schedule_status:     # delivery day -> schedule versions and TSO acknowledgement status
    backend: confirmed in blueprint
    mode: read
  list_open_clearing_items: # supplier or grid area -> unresolved clearing list entries
    backend: confirmed in blueprint
    mode: read
  get_portfolio_position:   # portfolio, period -> open position by product
    backend: confirmed in blueprint
    mode: read
  draft_clearing_response:  # clearing item -> proposed response for a person to confirm
    backend: confirmed in blueprint
    mode: propose
audit: every call logged with user, tool, arguments and the SOPTIM 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.

SOPTIM 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

Which balancing groups show MaBiS deviations above tolerance for last month?
What is the status of today's schedule submissions to each transmission system operator?
Which clearing list entries from supplier X are still unresolved?

What it will not do

Read more than the asking user may read in SOPTIM; permissions come from SOPTIM, not from the connector.
Send a schedule, a nomination or a clearing response: the only write tool returns a draft response that a person confirms and sends.
Replace forecasting: forecasts and price calculations stay with SOPTIM and esterion.

When this is the wrong page

If the task is moving files and data between systems on a schedule, ELEMENT:DataHub already does that inside SOPTIM. A connector is right when Claude, ChatGPT or Copilot has to answer a balancing, schedule or portfolio question on demand, under the asking user's own rights.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your SOPTIM owners and checks every backend against your release and licence. Week two tests whether a person's own SOPTIM 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 SOPTIM 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: SOPTIM: integration and APIs (Aug 2026) · SOPTIM Elements product world · Balancing group and schedule management · SOPTIM company · SOPTIM at E-world 2026. Read 21 September 2026. Vendor documentation changes; verify against the current release.

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

Questions SOPTIM teams ask before the first tool call

Does SOPTIM have its own MCP server?

Not as of 21 September 2026. SOPTIM's AI work runs through its subsidiary esterion for forecasts and price calculations, and we found no assistant or MCP server in the Elements product. An MCP server has to be built against the SOPTIM APIs your installation offers.

Do we need extra SOPTIM licences or access for an AI connector?

SOPTIM's API documentation comes with a customer or project relationship, and the terms are not public. Check with SOPTIM which APIs your Elements edition or VIM and PMS installation includes; the blueprint answers this before any tool is built.

Can the assistant see data a user is not allowed to see in SOPTIM?

No. The connector runs each call with the asking person's own SOPTIM rights, never a shared account with wider access. Two users asking the same question can get two different answers, and that is tested before go-live.

What does a SOPTIM connector cost?

The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.

Next step

Not a sales call. An architecture call.

Thirty minutes with the engineer who would build the connector, with your SOPTIM administrator in the room if you like.