Skip to main content
Glama
energidata-mcp

energidata-mcp

by batutho-dot

energidata-mcp

An MCP server that lets an AI assistant (Claude Code, Claude Desktop, any MCP host) look up Danish electricity data from Energinet's open Energi Data Service: the CO2 intensity of the power you use, the day-ahead spot price, and the cleanest or cheapest hours in a time window, for price area DK1 (West Denmark) or DK2 (East Denmark).

The question

Can a model answer "when is power cleanest or cheapest in Denmark?" correctly if it gets three small, well-described tools instead of the raw API? Checked on 10 questions with answers computed independently by a plain script.

Score: 10 out of 10 (Claude Sonnet 5.5 through Claude Code 2.1.314, 2026-11-19), after one fix to the server. Before the fix it was 9 out of 10; the miss was the server's arithmetic, not the model. Plain-script answers: 10 of 10 reproduced by the server tests.

Related MCP server: Energy Grid MCP Server

Run it (one command)

Needs uv. From a clone of this repository:

uvx --from . energidata-mcp

That builds a fresh environment and starts the server on stdio (it then waits silently for a host to talk to it). To add it to Claude Code:

claude mcp add energidata -- uvx --from /absolute/path/to/energidata-mcp energidata-mcp

Or with pip: pip install . then the command energidata-mcp.

How it works

An MCP server is a small program that an AI app starts in the background and talks to over stdin and stdout. The server announces its tools (name, description, typed arguments); the model decides when to call one, the app runs the call, and the result goes back to the model as text plus structured JSON. The server never talks to the model directly.

This one has three files:

File

Job

src/energidata_mcp/api.py

Fetches rows from the Energi Data Service API, caches them for 5 minutes, waits and retries once on a rate-limit answer (HTTP 429)

src/energidata_mcp/core.py

Pure functions: checks the time window, averages 5-minute or 15-minute rows into hours, picks the lowest or highest hours

src/energidata_mcp/server.py

The three tools, built with the official MCP Python SDK (MCPServer, v2.3)

The tools:

Tool

Answers

Dataset

co2_intensity(area, start, end, source)

g CO2/kWh per hour

CO2Emis (measured) or CO2EmisProg (forecast); auto picks measured for past windows

spot_price(area, start, end, currency)

DKK or EUR per MWh per hour

DayAheadPrices

best_hours(area, metric, start, end, n_hours, consecutive, highest)

the n cleanest or cheapest hours, or the best block of n back-to-back hours

as above

All times in and out are Danish local time. A window is start (inclusive) to end (exclusive); leave end out to get the rest of the start day. Wrong input (a bad date, an empty window) comes back as a tool error the model can read and fix.

The test set

eval/questions.json holds 10 questions on two fixed past days (17 and 18 November 2026), so the right answers do not move. eval/answers.py computes them straight from the API with the standard library only, using its own grouping code (by the Danish-time hour string, where the server groups by the UTC hour), so it checks the server's arithmetic rather than repeating it.

python eval/answers.py        # writes eval/expected.json, caches raw rows in eval/.cache/
pytest                        # 11 tests: the 10 questions through an in-memory MCP client, plus a bad-date case
python eval/agent_run.py      # asks Claude Code each question, records answers and tool calls
python eval/score.py          # scores eval/agent_results.json against eval/expected.json

Data completeness for the test window: 576 of 576 five-minute CO2 rows and 192 of 192 fifteen-minute price rows per area.

Results

Plain script (eval/answers.py, no model) and the agent, per question. The agent run used claude -p with only this server's three tools enabled (no shell, web or files), one fresh session per question. Rule set before the run: right when every required hour and number appears in the answer (eval/score.py).

#

Question (short)

Right answer (plain script)

Agent run 1

Agent run 2 (after fix)

Tool calls

1

CO2 DK1, 17 Nov, 08:00

189.83 g/kWh

right

co2_intensity

2

Cleanest hour DK2, 17 Nov

01:00 (24.58 g/kWh)

right

best_hours

3

Lower daily CO2, 18 Nov

DK1, 120.92 vs DK2 121.48 g/kWh

right

co2_intensity x2

4

Price DK1, 17 Nov, 18:00

1586.96 DKK/MWh

right

spot_price

5

Cheapest hour DK2, 18 Nov

04:00 (829.75 DKK/MWh)

right

best_hours

6

Dearest hour DK1, 18 Nov

18:00, 1574.96 DKK/MWh

right

best_hours (highest)

7

Cheapest 3 h block DK1, 17 Nov

starts 21:00, mean 1255.58 DKK/MWh

right

best_hours (consecutive)

8

Cleanest 3 h block DK2, 18 Nov

starts 08:00, mean 108.19 g/kWh

right (said mean 108.2)

right (108.19)

best_hours (consecutive)

9

4 cheapest hours DK1, 18 Nov, 06 to 22

06:00, 11:00, 12:00, 13:00

right

best_hours

10

Day mean DK2, 17 Nov, EUR

225.69 EUR/MWh

wrong (225.68)

right (225.69)

spot_price

Every question took exactly 1 tool call, except question 3 (2 calls, one per area). The model picked the right tool and arguments every time; it never needed a retry after a tool error. Raw answers and calls: eval/agent_results_run1.json (run 1) and eval/agent_results.json (run 1 with questions 8 and 10 replaced by run 2). The runs had my own global Claude Code instructions loaded, which is why some answers end with "Next:" or "Verified:" lines.

I also checked the extra numbers the model volunteered (day means, block hours) against the plain script. All were right except one: in run 2, question 10 said the day's low was 187.98 at 04:00; the real low was 156.40 at 23:00 (run 1 had it right). The model read that off the 24 hourly values itself. A strict grader counting side claims would give run 2's question 10 a fail, which makes it 9 of 10 again.

What did not work

  • My server rounded too early. The first version rounded each hourly value to 2 decimals and then averaged the rounded values. Day and block means came out 0.01 off on 2 of 10 questions (225.68 instead of 225.69, 108.20 instead of 108.19). The agent repeated the tool's number faithfully, so run 1 lost question 10. My own tests did not catch it because they allowed a 0.01 tolerance. Fixed: means now use unrounded hourly values, and the tests demand an exact match (checked: the old code fails 2 of the tightened tests).

  • A side claim was wrong even though the scored number was right (question 10, run 2, above). The tools return every hour, but nothing returns the minimum and maximum of a window, so the model scanned 24 numbers itself and picked the wrong one. A min/max field in the tool output would remove that step.

  • The rate limit dominates the waiting time. The first draft of the answer script hit HTTP 429 twice and had to wait 62 seconds each time.

  • The SDK changed under older examples. Older MCP examples use FastMCP; version 2 of the official Python SDK uses MCPServer. This server was written from the current SDK docs, not from older examples.

Limits

  • Rate limit. The API allows very few uncached calls: after one call a dataset answered with the header RemainingCalls: 0, and the next call got HTTP 429 "Try again in N seconds" (about 60 seconds when measured). The server caches for 5 minutes and waits once, so a question that needs two areas can take a minute. It is not built for polling.

  • Hourly values are averages. Prices are published per 15 minutes and CO2 per 5 minutes; every hourly value here is the plain mean of the rows in that hour. The day average is the mean of the hourly values.

  • Prices start 2025-10-01. Older prices are in the discontinued Elspotprices dataset, which this server does not read.

  • CO2 data is initial data. Energinet says the 5-minute CO2 series comes from upscaled real-time measurements and that errors "will generally not be corrected"; the corrected figures are in the DeclarationGridEmission dataset, not used here. The forecast tool path (CO2EmisProg) is not covered by the test set, because a forecast has no fixed answer.

  • Spot price only. No taxes, tariffs or grid fees; this is not what a household pays.

  • "Now" is judged on the machine's clock in Danish time, only to choose measured versus forecast CO2 when source="auto".

Data source and licence

Data: Energinet, Energi Data Service, datasets CO2Emis, CO2EmisProg and DayAheadPrices. Published under CC BY 4.0 per the terms and conditions. Source: Energinet (www.energidataservice.dk). Changes made here: sub-hourly values are averaged into hours. Energinet does not endorse this project. No data is stored in this repository except the computed answers in eval/expected.json.

Code: MIT, see LICENSE.

Available Tools

3 tools
best_hoursA

Find the cleanest (lowest CO2) or cheapest hours in a window, e.g. when to run a heat pump or charge a car.

metric: 'co2' or 'price'. n_hours: how many hours to pick. consecutive=True returns the block of n back-to-back hours with the lowest mean instead of the n lowest single hours. highest=True flips it to the dirtiest / most expensive hours. Times are Danish local time.

Inputs: area (required), start (required), metric (required), end, +5 more. Returns: object

co2_intensityA

CO2 intensity of electricity consumed in a Danish price area, per hour, in g CO2 per kWh.

start/end: Danish local time, '2026-11-17' or '2026-11-17T06:00'; end is exclusive and defaults to the next midnight. source: 'measured' (CO2Emis), 'forecast' (CO2EmisProg), or 'auto' = measured when the window is in the past, otherwise forecast. Each hour is the mean of the 5-minute values in it; 'samples' says how many there were (12 = complete).

Inputs: area (required), start (required), end, source. Returns: object

spot_priceA

Day-ahead (spot) electricity price in a Danish price area, per hour, per MWh, before taxes and tariffs.

start/end: Danish local time, '2026-11-17' or '2026-11-17T06:00'; end is exclusive and defaults to the next midnight. Each hour is the mean of the four 15-minute prices in it. Data from the DayAheadPrices dataset, available from 2025-10-01; tomorrow's prices appear around 13:00.

Inputs: area (required), start (required), end, currency. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly distinct concern: raw CO2 intensity series, raw spot price series, and an optimization/selection query. Although best_hours draws on the same data as the other two, its purpose (picking hours) is unambiguous and descriptions make the boundary explicit.

    Naming Consistency5/5

    All three names are lowercase snake_case noun phrases with no mixed conventions: co2_intensity, spot_price, best_hours. Predictable and readable.

    Tool Count4/5

    Three tools is well-scoped for a narrow domain (two data series plus a selection helper), with no redundancy. It sits near the thin edge — a bare minimum surface for a data server.

    Completeness4/5

    The core lifecycle (fetch CO2, fetch price, pick optimal hours) is covered with sensible parameters like metric, n_hours, consecutive, and source. Minor gaps exist: no way to list available price areas, no finer-than-hourly resolution option, and no combined CO2+cost ranking for best_hours.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides access to Danish energy data from Energinet, including real-time electricity spot prices, CO2 emissions, and production mix. It enables users to monitor grid status and identify the most cost-effective hours for energy-intensive tasks.
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides real-time electricity grid data including CO2 intensity, power mix, and wholesale prices, plus optimal green time windows for energy-intensive AI tasks. Supports UK, Germany, and global regions with optional API keys.
      9
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to query current and historical UK electricity carbon intensity, generation mix, and regional intensity data to schedule energy-intensive tasks during low-carbon periods.
      90 npm
      MIT