GridHub Electricity Market Data
RemoteAbout GridHub Electricity Market Data
GridHub MCP Server provides AI agents with live and historical electricity market data across 25 grid zones in a normalized JSON format. It also reports carbon intensity for Great Britain and includes source licensing and attribution.
Key features
- 01Query current prices and demand
- 02Retrieve up to 31 days of metric history
- 03Compare headline data across 25 zones
- 04Check source status and licensing
Use cases
- 01Compare prices and demand across zones
- 02Check Great Britain’s electricity carbon intensity
- 03Analyze historical changes in a metric
MCP support
The service exposes tools through a stateless Streamable HTTP MCP endpoint, allowing MCP clients to query prices, demand, carbon intensity, and source information.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.grid-hub.app/mcpclaude mcp add --transport http jalcodev-gridhub https://api.grid-hub.app/mcp{"mcpServers":{"jalcodev-gridhub":{"type":"http","url":"https://api.grid-hub.app/mcp"}}}Open in Cursor{"servers":{"jalcodev-gridhub":{"type":"http","url":"https://api.grid-hub.app/mcp"}}}Open in VS Code{"mcpServers":{"jalcodev-gridhub":{"type":"http","url":"https://api.grid-hub.app/mcp"}}}{"mcpServers":{"jalcodev-gridhub":{"serverUrl":"https://api.grid-hub.app/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://api.grid-hub.app/mcpAuth requiredTools
6This tool takes no parameters.
Details
From the project READMEGridHub MCP Server
Live and historical electricity market data for AI agents, over the Model Context Protocol.
Endpoint: https://api.grid-hub.app/mcp — hosted, Streamable HTTP, stateless. Nothing to install.
Covers 25 grid zones — US ISOs (CAISO, ERCOT, PJM, MISO, NYISO, ISO-NE, SPP), 12 European bidding zones, Great Britain, and the five Australian NEM regions — normalised into one JSON schema. Sourced from EIA, ENTSO-E, NESO, Elexon and AEMO; every response carries its licence and attribution.
Tools
| Tool | What it returns |
|---|---|
get_zone_brief | Current price / demand (and carbon intensity for GB) ranked against the zone's own last 30 days (percentile, vs-median, min/max), 24h trend, generation mix (GB, US-CAISO), and a one-sentence summary. Best for "is electricity cheap or clean in X right now?" |
get_latest | Most recent value of every metric one zone publishes, with unit and timestamp |
get_history | Time series for one metric over a start/end window (up to 31 days per call) |
get_map_snapshot | Headline values for all 25 zones at once — compare or rank zones |
list_zones | Zone ids, names, sources, currencies, licences (free) |
get_status | Ingestion freshness per source and zone (free) |
Access
Three levels, no signup needed to start:
- Sample mode — connect with no credentials. Tools return real, current data, truncated (history capped at 50 rows; brief returns one context block). Results are clearly marked.
- Free API key — 500 requests/day. Instant email signup at grid-hub.app/developers, or
POST https://api.grid-hub.app/v1/keys/signupwith{"email": "..."}. Send asAuthorization: Bearer <ghk_key>. - x402 pay-per-call — USDC on Base, $0.001–$0.02 per call, via the
X-PAYMENTheader. See the x402 flow.
Setup
Claude Code
claude mcp add --transport http gridhub https://api.grid-hub.app/mcp \
--header "Authorization: Bearer YOUR_KEY"
Cursor / Windsurf / VS Code (mcp.json)
{
"mcpServers": {
"gridhub": {
"url": "https://api.grid-hub.app/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
}
Claude Desktop / claude.ai — add https://api.grid-hub.app/mcp as a custom connector. These clients don't send custom headers; pass the key as the optional api_key tool argument, or use sample mode.
Local stdio bridge — for clients that only support local (stdio) servers. It proxies to the hosted endpoint via mcp-remote; nothing runs locally except the bridge.
{
"mcpServers": {
"gridhub": {
"command": "npx",
"args": ["-y", "github:jalcodev/gridhub-mcp"],
"env": { "GRIDHUB_API_KEY": "YOUR_KEY" }
}
}
}
Or with Docker: docker build -t gridhub-mcp . && docker run -i -e GRIDHUB_API_KEY=YOUR_KEY gridhub-mcp. Omit the key for sample mode.
Any client, no key — omit the header. You'll get sample-mode data and a note on how to upgrade.
Protocol
- Streamable HTTP, stateless: one JSON-RPC message per POST, JSON response. No sessions, no SSE.
- Speaks MCP
2026-07-28(header-mirrored requests, no handshake) and2025-03-26through2025-11-25(initializehandshake). - Tool results include
structuredContentalongside the text block. - Rate limits and quotas are those of the underlying REST API; the MCP layer adds none of its own.
Related
- REST API docs: https://grid-hub.app/developers
- OpenAPI: https://api.grid-hub.app/openapi.json
llms.txt: https://api.grid-hub.app/llms.txt- Official MCP Registry entry:
io.github.jalcodev/gridhub
License
The code in this repository is MIT licensed. Data returned by the service is subject to each source's licence, stated in every response (license and attribution fields).
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.