Odel
Energy Charts

Energy Charts

@pipeworx-ioTypeScriptMITUpdated 1w ago

Energy-Charts (Fraunhofer ISE) MCP — European electricity generation, prices, and capacity.

Server endpointStreamable HTTPNo authProbed

This is the third-party server itself — Odel doesn't run it. Hitting this URL directly talks straight to the upstream server with no auth or proxying. Connect through Odel to front it with managed auth.

mcp-energy-charts

Energy-Charts (Fraunhofer ISE) MCP — European electricity generation, prices, and capacity.

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

Tools

ToolDescription
generation_mixThe CURRENT ELECTRICITY GENERATION MIX BY FUEL for a European country — how much power is coming from solar, wind, nuclear, gas, coal, hydro, biomass right now, with each fuel's MW and percentage share. Answers "what is Germany's generation mix", "how much of France's electricity is nuclear", "Germany power generation by source", "what fuels are generating electricity in ". Accepts a country NAME ("Germany", "France") or 2-letter code. Also returns renewable vs fossil vs nuclear totals. Source: Fraunhofer ISE energy-charts, keyless.
public_powerElectricity generation broken down by production type (solar, wind, nuclear, gas, etc.) for a country over a date range. Returns {unix_seconds, production_types:[{name, data}]}; each series' data array is timestamp-aligned to unix_seconds. Power in MW.
electricity_priceDay-ahead spot electricity prices for a bidding zone over a date range. Returns {unix_seconds, price, unit}; the price array is timestamp-aligned to unix_seconds. Prices in EUR/MWh.
total_powerTotal electricity generation / load for a country over a date range. Returns {unix_seconds, production_types:[{name, data}]}; data arrays are timestamp-aligned to unix_seconds. Power in MW.
installed_powerInstalled generation capacity by production type for a country, as an annual or monthly series. Returns {time:["2002",...], production_types:[{name, data}]}; data arrays are aligned to the time array. Capacity in GW.
renewable_shareRenewable share of a country's electricity load — what share / percent of load is currently being covered by renewables (wind, solar, hydro combined). Keyless, no API key. Answers "what share of Germany's electricity load is renewable right now". Returns a list of series [{name, data, ...}] where each data point is a percent of load; values are timestamp-ordered, most recent last (read the last value for the current share). Dates optional (defaults to the last 7 days).

Quick Start

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

{
  "mcpServers": {
    "energy-charts": {
      "url": "https://gateway.pipeworx.io/energy-charts/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/energy-charts/mcp returns the tools in the table above plus the shared Pipeworx meta-toolsask_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 Energy Charts data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT