Ofgem MCP server

@pipeworx/ofgem

Ofgem energy data — the UK energy regulator's published statistics on the domestic price cap and what it is made of, wholesale gas and electricity prices, supplier market shares, switching, debt and customer service, returned as tabular rows rather than pictures.

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

Tools

Returns dataset_id, the id every other tool here takes.

• ofgem_datasets(query?, page?) — the Data Portal catalogue (~190 datasets).

period, broken into wholesale / network / policy / operating / debt / EBIT / VAT components, for Direct Debit, prepayment or standard credit.

• ofgempricecap(payment_method?, periods?) — the default tariff cap by

table behind any Data Portal dataset.

• ofgemdatasetrows(datasetid, limit?, latestfirst?) — the full source

Auth

Keyless.

Data sources

• — the Data Portal chart catalogue.
• — the source table for one dataset.

Things worth knowing:

does not resolve at all (no A record; it has MX records only). /jsonapi, /api/v1/datasets and /api/search are 404s. The Data Portal page renders nothing server-side — a plain fetch of /news-and-insight/data/data-portal/all-available-charts contains zero dataset links, so scraping the HTML returns an empty list, not an error.

• There is no CKAN, no Opendatasoft and no JSON:API. data.ofgem.gov.uk

own front end calls (found in themes/custom/numiko/dist/filter-listing-legacy-*.js). 2156 is the chart listing's paragraph id. It takes fulltext= and page= (0-based, 24 per page) and reports the match count in meta.count.

• The catalogue is /api/listing/{paragraphid}**, the endpoint the portal's

a data-js-chart-modal-data attribute on the row's teaser markup, not as a JSON field. It has to be unescaped and parsed out.

• Each catalogue row carries its dataset payload as HTML-escaped JSON inside

everviz (Highsoft), and the everviz embed script carries the source table as CSV in options.data.csv. That CSV is the data; this pack parses it.

• The table is not on ofgem.gov.uk. Ofgem publishes each dataset through

British, and the price-cap breakdown tables use period labels ("Oct - Dec 2026") rather than dates. Row labels are returned verbatim.

• Dates in those CSVs are US-ordered (mm/dd/yyyy) even though every figure is

Blank-named columns are dropped; duplicate names get a (2) suffix so one column never silently swallows its neighbour.

• CSV headers repeat and some are blank spacers used for chart layout.

falls back to the known everviz ids, so an upstream rename degrades to a stale id rather than to no answer.

• ofgempricecap resolves its dataset from the live catalogue first and only

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "ofgem": {
      "url": "https://gateway.pipeworx.io/ofgem/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/ofgem/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.