For teams running XENON

A gridX API and MCP server that reads system measurements on the customer's own XENON account

Pexon builds a gridX API connector so Claude, ChatGPT or Copilot can read systems, live measurements and historical measurements on the customer's own XENON account. The OpenAPI file linked from the developer documentation, last updated on 11 November 2026, names the production host api.gridx.de. No gridX MCP server was named on the pages opened on 15 November 2026.

gridXlist_systemsget_system_liveget_system_historicalAgentruns as theperson asking

What we build

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

Built on what gridX GmbH documents: systems, live measurements, historical measurements, assets, gateways, appliances. 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.

# gridx-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_systems:          # token's account -> systems and list metadata
    backend: GET /systems/list
    mode: read
  get_system_live:       # system id -> latest aggregated measurement
    backend: GET /systems/{systemID}/live
    mode: read
  get_system_historical: # system id, ISO8601 interval, resolution -> aggregated measurements
    backend: GET /systems/{systemID}/historical
    mode: read
  list_assets:           # system id -> assets on that system
    backend: GET /systems/{systemID}/assets
    mode: read
  list_gateways:         # token's account -> gateways
    backend: GET /gateways
    mode: read
  list_appliances:       # gateway id -> appliances, children only when listAll is true
    backend: GET /gateways/{gatewayID}/appliances
    mode: read
audit: every call logged with user, tool, arguments and the gridX 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.

Checked 15 November 2026

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

What we found
InterfacesgridX API (REST/JSON, docs public) · Webhook subscriptions (REST/JSON, docs public)
AuthenticationThe OpenAPI security scheme says the Authorization header takes a JWT with the prefix Bearer or an API token with the prefix Token. The organizational-token post says the bearer token is a short-lived JWT from a Xenon login, and an organizational token is tied to one account and only the policy groups named when it is created. A token with no groups has no permissions. The connector calls api.gridx.de with the customer's token.
Vendor MCP serverNo vendor server. No gridX MCP server is named on the API page, the about page, the imprint, the documentation topic, the rename announcement or the organizational-token post, all read on 15 November 2026. A GitHub search that day for mcp inside the grid-x organization returned no repository. A phrase search for gridx mcp server did not return a gridX GmbH server. One hit describes GridX Inc. of Walnut Creek, a different company.
Vendor AI assistantNone found.
Other connectorsNo gridX GmbH MCP server was in the repository searches on 15 November 2026. The phrase search returned a profile of GridX Inc. in Walnut Creek, which is a different company, and unrelated weather servers.

gridX GmbH (DE). Companies that use XENON for residential energy management and e-mobility. The about page, read on 15 November 2026, describes XENON that way, and the imprint the same day names gridX GmbH in Aachen. No installed-base count was on the pages opened. The API page the same day says 50 million API calls per day as of July 2025, and 230 members in the developer forum. Those figures are the vendor's. A data-saving figure on that page was still an unfilled placeholder.

Why gridX is hard for agents

Where a gridX connection needs engineering, not configuration

01 · Units

Resolution decides whether the number is watts or watt-hours

Historical measurements use 15m and 1h for power in W, and 1d, 1w and 1M for energy in Wh. The interval cap is one day at 15m, one week at 1h, one month at 1d or 1w, and five years at 1M. On a live measurement, positive grid power is supply and negative grid power is feed-in.

02 · Token

An empty group list cannot read the account

A bearer JWT comes from a Xenon login and is short-lived. An organizational token uses the prefix Token, belongs to one account, and only has the policy groups set when it is created. The token post says a token with no groups has no permissions. The connector does not invent a read-only group name. It uses the customer's token against api.gridx.de.

03 · Window

Asset and appliance history stops at 24 hours

Asset measurements need a start and an end, and that range must be no longer than 24 hours. Combined appliance measurements refuse an interval longer than 24 hours, and only for types INVERTER, METER, EVSTATION and HEAT_PUMP. Children of a hybrid inverter are omitted unless listAll is true. The longer record is the system historical operation, inside the resolution caps.

04 · Writes

Power limits and schedules are in the file and off the manifest

The same OpenAPI file documents POST for a new system, PUT for import and export power limits, and writes for power-limit schedules, tariffs, time-of-use settings and webhook subscriptions. None of those is a tool.

One interface per row

How the gridX interfaces differ

01

gridX API

REST/JSON. Documentation is public. OpenAPI read on 15 November 2026, file stamped 11 November 2026. Production host api.gridx.de. 74 GET operations counted in that file. Responses use application/vnd.gridx.v2+json

REST/JSON. Docs public.

02

Webhook subscriptions

REST/JSON. Documentation is public. the same file documents account webhook paths. Creating a subscription is a POST. No webhook path is a tool, and no event-type list was opened

REST/JSON. Docs public.

gridX 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 is the latest aggregated measurement on this system?
  • What aggregated measurements did this system return for this interval and resolution?
  • Which assets belong to this system?

What it will not do

  • Set an import or export power limit, a power-limit schedule, a tariff or a time-of-use setting. Those methods are in the OpenAPI file and stay off the manifest.
  • Create a system, a webhook subscription or a token.
  • Read an asset measurement range longer than 24 hours, or a combined appliance measurement interval longer than 24 hours. The file states both caps.

When this is the wrong page

If the plants are in SMA Sunny Portal or ennexOS, the SMA Monitoring connector reads them on the plant owner's consent. If the record is a Smallworld network feature, use that connector. gridX reads systems and measurements on the customer's own XENON account at api.gridx.de. Power limits and schedules stay off this page. No gridX MCP server was named on the pages read on 15 November 2026. GridX Inc. of Walnut Creek is a different company.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your gridX owners and checks every backend against your release and licence. Week two tests whether a person's own gridX 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 gridX 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: API documentation · gridX API OpenAPI · Organizational tokens · XENON API rename · gridX API · About gridX · Imprint. Read 15 November 2026. Vendor documentation changes; verify against the current release.

Questions gridX teams ask before the first tool call

Does gridX ship an MCP server for XENON?

Not one that was named on the API page, the about page, the imprint, the documentation topic, the rename announcement or the organizational-token post, all read on 15 November 2026. A GitHub search that day inside the grid-x organization returned no MCP repository. A phrase search did not return a gridX GmbH server. One result describes GridX Inc. of Walnut Creek, a different company.

What can an assistant read from the gridX API?

Systems the token can access, the latest aggregated measurement, historical measurements for an interval and a resolution, assets on a system, gateways, and appliances on a gateway. The OpenAPI file read on 15 November 2026 documents those GET paths. Power limits, schedules, tariffs and webhook creation stay off the manifest.

Whose permission does the gridX connector use?

The customer's. The security scheme accepts a Bearer JWT from a Xenon login or a Token-prefixed API token. An organizational token belongs to one account and only the policy groups named when it is created. The token post says a token with no groups has no permissions.

What does a gridX connector cost?

The two-week Readiness Blueprint is fixed at €4,900: the tool list, the account's policy groups, 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 gridX administrator in the room if you like.