For grid operators and suppliers running Robotron ecount

A Robotron ecount MCP server that answers from your energy data under each user's own rights

A Robotron ecount MCP server gives Claude, ChatGPT or Copilot named tools for load profiles, substitute values, balancing group sums and esales offers. Robotron publishes no general API; the read path is its Oracle or PostgreSQL data model. Robotron ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.

Why Robotron ecount is hard for agents

Where a Robotron ecount connection needs engineering, not configuration

01 · Access

The realistic read path is the database

Robotron publishes no general API reference. The practical read path is the Oracle or PostgreSQL data model, which needs Robotron's schema knowledge and carefully scoped read-only grants.

02 · Volume

Quarter-hour time series are large

Load profiles at 15-minute resolution produce large volumes. Tools aggregate on the server, by day or by peak, before anything reaches the language model.

03 · Modules

Every installation has different modules

ecount, esales and the other modules are licensed separately, so the available tables and functions differ from customer to customer. The tool list is fixed per installation in the blueprint.

04 · Market

Market communication is off limits

MSCONS, ALOCAT and AS4 traffic are regulated processes with deadlines. An agent reads their status at most and never triggers a send.

Checked 21 September 2026

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

	What we found
Interfaces	EDM core database (database (Oracle or PostgreSQL), docs not published): all modules share one data model; Robotron names Oracle and PostgreSQL, the schema is not published · esales web service connection (web services, type not published, docs not published): named in the esales flyer for connecting external forecast models, next to an R interface for custom figures · Market interfaces (BDEW API web services, AS4, MSCONS, UTILMD) (market standards, docs public): public market formats for control commands and market communication; these are market interfaces, not a general data API
Authentication	Not documented publicly. Check with Robotron which read access your installation allows.
Vendor MCP server	No vendor server. No Robotron MCP server found; Robotron is building an SQL chatbot for ecount and esales that turns questions into SQL.
Vendor AI assistant	An SQL chatbot for ecount and esales, machine-learning consumption forecasts, anomaly detection in scheduler jobs and the EVA system chatbot.
Other connectors	esales has standard interfaces to the trading platforms enmacc and Trayport; they are trading interfaces, not AI connectors.

Robotron Datenbank-Software GmbH (DE). German grid operators (robotron*ecount), energy retailers and procurement teams (robotron*esales) and metering point operators, from municipal utilities to large operators; Robotron calls ecount the market-leading energy data management system in Germany.

What we build

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

Robotron Datenbank-Software GmbH does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.

# robotron-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_load_profile:            # metering point, period, resolution -> aggregated time series
    backend: confirmed in blueprint
    mode: read
  list_substitute_values:      # period, grid area -> metering points with substitute values and method
    backend: confirmed in blueprint
    mode: read
  get_balancing_group_summary: # balancing group, day -> allocated quantities
    backend: confirmed in blueprint
    mode: read
  list_open_offers:            # status filter -> offers with customer, volume, margin
    backend: confirmed in blueprint
    mode: read
  draft_plausibility_note:     # metering point, finding -> proposed correction note for a person to confirm
    backend: confirmed in blueprint
    mode: propose
audit: every call logged with user, tool, arguments and the Robotron ecount 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.

Robotron ecount 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 metering points had substitute values generated this week, and by which method?
Show the load profile of metering point X for last month with daily peaks.
Which offers in esales are still open, and what is their contribution margin?

What it will not do

Read more than the asking user may read; access follows that person's rights, not a shared database account.
Correct a value by itself: the only write tool returns a plausibility note that a person confirms.
Send or trigger any market communication message.

When this is the wrong page

If your analysts only want to query ecount or esales in plain language, check with Robotron first whether its SQL chatbot is available for your installation. A connector is right when Claude, ChatGPT or Copilot has to combine energy data with other systems, under each user's own rights.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your Robotron ecount owners and checks every backend against your release and licence. Week two tests whether a person's own Robotron ecount 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 Robotron ecount 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: Robotron: grid operators · robotron*ecount flyer (PDF) · robotron*esales flyer (PDF) · Robotron: AI in the energy industry. 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 Robotron ecount teams ask before the first tool call

Does Robotron ecount have its own MCP server?

Not as of 21 September 2026. Robotron is building an SQL chatbot for ecount and esales that turns questions into SQL, but it is not an MCP server for outside assistants. Check with Robotron whether the chatbot is available for your installation.

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

The modules are licensed separately and the data model is not published, so this is a question for Robotron. Check with Robotron which read access and schema documentation you can get; the blueprint answers this before any tool is built.

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

No. The connector applies the asking person's own rights, not a shared database account with full access. Two users asking the same question can get two different answers, and that is tested before go-live.

What does a Robotron ecount 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 Robotron ecount administrator in the room if you like.