Elexon MCP server

@pipeworx/elexon

Elexon BMRS Insights MCP — Great Britain electricity grid and wholesale market data. Keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

• generationbyfuel(from, to) — half-hourly GB generation in MW per fuel type (FUELHH), plus a byFuel total per fuel over the window.
• system_demand(from, to) — half-hourly GB transmission system demand outturn in MW (ITSDO).
• elexonlistdatasets(search?) — the directory of all 84 BMRS datasets: code, title, and which window parameters its route takes. Search by keyword ("wind", "price", "forecast") to find a code before calling query_dataset.
• querydataset(dataset, from, to, settlementperiod?, date_param?) — records from any of the 84 datasets by code. The correct window parameters are chosen per dataset automatically.
• elexonsystemprices(settlementdate, settlementperiod?) — GB imbalance prices (system buy / system sell, GBP/MWh) per settlement period, with net imbalance volume and price derivation code (DISEBSP). Elexon serves this outside /datasets, so query_dataset cannot reach it.

A GB settlement day has 48 half-hour settlement periods.

Auth

None. No key, no signup, no quota we have hit.

The 404 that means two different things

Elexon answers 404 {"statusCode":404,"message":"Resource not found"} for both an unknown dataset code and a known code queried with the wrong window parameters, because the window parameters are part of route resolution. /datasets/MID?publishDateTimeFrom=... is a 404 even though MID exists and is one of the most-wanted datasets in the pack — MID's route takes from/to.

That is why this pack carries a DATASETS table instead of passing the code straight through. It maps each of the 84 codes to one of five window styles:

Consequences worth knowing:

time, so querydataset needs settlement_period (1–48) for those. It says so by name rather than 404ing.

• The six settlementDate datasets are served **one settlement period at a

the near-matches and the full code list in the message. It never books as a Pipeworx defect (fleet #584: 49 identical 404s in three hours, every one a caller guessing a code, all filed as our bug).

• An unrecognised code is rejected by the pack, before the upstream call, with

get a 404 from a code that exists, the window parameters were what was rejected.

• A real code with an empty window returns zero records, not a 404. If you

"settlement" means settlementDateFrom/To, which only FUELHH and FUELINST accept; "settlementDate" is the per-period style above.

• date_param overrides the lookup and is rarely needed. The legacy value

What callers actually guess

Measured from a day of live traffic, two classes of guess account for most of the wasted calls, and the pack now answers both:

Shortened. The full README is on GitHub.