About voltcast
voltcast is an MCP server for European electricity market data, forecasts, carbon intensity, and load-window optimization. Energy analysts and operators can access prices across 47 bidding zones, with forecast accuracy published daily.
Key features
- 01Day-ahead prices across 47 zones
- 0215-minute native price resolution
- 03Probabilistic price forecasts
- 04Carbon intensity and green score
- 05Wind and solar forecasts
- 06Cheapest load window optimization
Use cases
- 01Review day-ahead prices by zone
- 02Compare forecasts with realized prices
- 03Check carbon intensity and renewables
- 04Find a low-cost window for a load
MCP support
Exposes electricity prices, forecasts, carbon and renewable data, zone listings, and cheapest-window optimization to MCP clients. Clients can connect to its hosted Streamable HTTP endpoint or run the local stdio proxy.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://voltcast.com/api/mcpclaude mcp add --transport http com-voltcast-voltcast https://voltcast.com/api/mcp{"mcpServers":{"com-voltcast-voltcast":{"type":"http","url":"https://voltcast.com/api/mcp"}}}Open in Cursor{"servers":{"com-voltcast-voltcast":{"type":"http","url":"https://voltcast.com/api/mcp"}}}Open in VS Code{"mcpServers":{"com-voltcast-voltcast":{"type":"http","url":"https://voltcast.com/api/mcp"}}}{"mcpServers":{"com-voltcast-voltcast":{"serverUrl":"https://voltcast.com/api/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.
Tools
7This tool takes no parameters.
Details
From the project READMEVoltcast MCP Server — European electricity prices, forecasts & carbon
Model Context Protocol server for Voltcast: day-ahead electricity prices for 47 European bidding zones (15-minute native resolution, history to 2015), probabilistic price forecasts whose accuracy is published daily at voltcast.com/accuracy, carbon intensity, and cheapest-window optimization.
Two ways to run it:
1. Hosted endpoint (recommended)
https://voltcast.com/api/mcp
Streamable HTTP transport, protocol 2025-06-18. Server card:
/.well-known/mcp.json.
2. Local stdio server (this repo)
VOLTCAST_API_KEY=your_key npx voltcast-mcp
Or with Docker:
docker build -t voltcast-mcp .
docker run -i -e VOLTCAST_API_KEY=your_key voltcast-mcp
The stdio server is a thin proxy onto the same REST API — identical tools,
auth and rate limits. It starts and answers introspection without a key;
list_zones works keyless too.
{
"mcpServers": {
"voltcast": {
"command": "npx",
"args": ["voltcast-mcp"],
"env": { "VOLTCAST_API_KEY": "YOUR_API_KEY" }
}
}
}
Tools
| Tool | Auth | What it does |
|---|---|---|
list_zones | none | The zone registry (codes, names, currencies) |
get_prices | key | Day-ahead prices for a zone/date at native market intervals |
get_forecast | key | P50 on Home/Starter and P10/P90 on Pro+ |
get_carbon | key | Carbon intensity + green score from the live generation mix |
get_renewables | key | Wind/solar forecasts (TSO + Voltcast model) vs realized |
cheapest_window | Pro+ key | Cheapest contiguous window for a load in the next 48h |
Auth
Authorization: Bearer <api key>. New accounts start with
Home
at €9/month after a 7-day card-required trial; existing Free accounts remain
grandfathered. list_zones works without a key. The exact hosted-connector
walkthrough is at
voltcast.com/ai/local-electricity-price.
Client config
{
"mcpServers": {
"voltcast": {
"url": "https://voltcast.com/api/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
Honesty, stated plainly
Every forecast the server returns is benchmarked daily against a naive baseline in public — losses included. Zones where the model loses are free to use under the guarantee. Data sources: ENTSO-E Transparency Platform, SMARD.de (CC BY 4.0), attributed in every response.
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.