mcp-neso
OfficialProvides access to National Grid ESO (NESO) Great Britain electricity grid open data, enabling searches for datasets, listing of resources, querying of data, and retrieval of day-ahead demand forecasts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-nesowhat's the current GB electricity generation mix?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-neso
NESO MCP — Great Britain electricity grid open data (api.neso.energy)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
Tool | Description |
| Search NESO (National Energy System Operator, ex National Grid ESO) open data for UK electricity grid datasets — GB power demand forecasts, wind generation forecasts, carbon intensity, balancing costs, historic demand, energy system data. Returns dataset slug/id, title, summary, and resource count. Example: neso_search_datasets({ query: "wind forecast" }) |
| List the resources (data files/tables) inside one NESO UK electricity grid dataset by its id or slug (from neso_search_datasets). Returns the dataset title/description plus each resource's resource_id, name, format, datastore availability, and last_modified — pick a resource_id with datastore_active for neso_query_data. Example: neso_dataset_resources({ id: "14-days-ahead-wind-forecasts" }) |
| Query rows from a NESO GB energy dataset resource (CKAN DataStore) by resource_id — UK electricity demand, wind generation forecasts, carbon intensity, balancing data. Supports exact-match filters (field->value object), full-text query, limit, offset. Returns field names/types plus records. Example: neso_query_data({ resource_id: "aec5601a-7f3e-4c4c-bf56-d8e4184d3c5b", limit: 20 }) |
| Current GB day-ahead national electricity demand forecast from NESO (National Grid ESO) — tomorrow's UK power demand in MW at each cardinal point (the daily peaks and troughs the grid operator forecasts, with start/end times). Answers "what is tomorrow's UK electricity demand", "GB power demand forecast", "National Grid demand peak". Example: neso_demand_forecast({}) |
Related MCP server: Luminus
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"neso": {
"url": "https://gateway.pipeworx.io/neso/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/neso/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, 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.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Neso data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Query Australia's electricity market (NEM/AEMO): prices, generation, FCAS, interconnectors, bids.
Live and historical electricity prices and demand for 25 grids; carbon intensity for GB.
European power-market data: day-ahead & balancing prices, load, generation, flows, outages. 47 zones
GridStatus MCP — wraps the GridStatus.io REST API (api.gridstatus.io/v1)
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to query the UK National Grid's carbon intensity data, providing real-time and forecasted carbon emissions for electricity generation.7 npmMIT
- AlicenseBqualityAmaintenanceProvides real-time European and GB electricity grid data via MCP, including generation, prices, carbon intensity, and grid infrastructure.4445 npm6MIT
- FlicenseNot gradedqualityDmaintenanceProvides access to the UK Carbon Intensity API, enabling users to retrieve current, historical, and forecast carbon intensity data, regional data by postcode, and generation mix information.-
- AlicenseNot gradedqualityCmaintenanceEnables querying European electricity generation, prices, and capacity data from Fraunhofer ISE's Energy-Charts platform.13 npmMIT