com.voltcast/voltcast

Official registry E-commerce

European day-ahead electricity prices (43 zones), accuracy-published forecasts, carbon, optimize.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http voltcast 'https://voltcast.com/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "voltcast": {
            "type": "http",
            "url": "https://voltcast.com/api/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Voltcast MCP Server — European electricity prices, forecasts & carbon
  2. 1. Hosted endpoint (recommended)
  3. 2. Local stdio server (this repo)
  4. Tools
  5. Auth
  6. Client config
  7. Honesty, stated plainly

Voltcast 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:

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

ToolAuthWhat it does
list_zonesnoneThe zone registry (codes, names, currencies)
get_priceskeyDay-ahead prices for a zone/date at native market intervals
get_forecastkeyP50 on Home/Starter and P10/P90 on Pro+
get_carbonkeyCarbon intensity + green score from the live generation mix
get_renewableskeyWind/solar forecasts (TSO + Voltcast model) vs realized
cheapest_windowPro+ keyCheapest 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.

Frequently asked questions

What is com.voltcast/voltcast?

European day-ahead electricity prices (43 zones), accuracy-published forecasts, carbon, optimize.

How do I install com.voltcast/voltcast?

It runs as a remote server. In Claude Code: claude mcp add --transport http voltcast 'https://voltcast.com/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does com.voltcast/voltcast need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is com.voltcast/voltcast open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains com.voltcast/voltcast?

It is published by Voltcast-com. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.