🇨🇭 Part of the Swiss Public Data MCP Portfolio

⚡ swiss-energy-mcp

MCP server for Swiss energy data from the Federal Office of Energy (SFOE/BFE) via GeoAdmin REST API and opendata.swiss — no API key required.

🇩🇪 Deutsche Version

Overview

swiss-energy-mcp gives AI assistants structured, location-based access to Switzerland's energy infrastructure. Built on open geodata from the Swiss Federal Office of Energy (SFOE/BFE) via the GeoAdmin REST API and the opendata.swiss catalogue — completely authentication-free.

The server is part of a growing portfolio of Swiss open data MCP servers. Think of it as the energy atlas counterpart to swiss-road-mobility-mcp: while the latter maps mobility, this server maps where Switzerland produces electricity, where solar potential exists, and which municipalities hold the "Energiestadt" label.

Anchor demo query: "Which power plants are within 20 km of the school in Wädenswil — and is the municipality an Energiestadt?"

Features

• 🔍 10 ready-to-use tools covering all major energy data layers from SFOE/BFE
• ⚡ Power plants — all types: photovoltaic, hydro, wind, biomass, nuclear, with optional category filter
• 💨 Wind turbines — detailed data incl. manufacturer, model, hub height, annual production
• 💧 Hydropower plants — type, status, turbine capacity, expected annual output
• ☀️ PV large installations — project name, capacity, annual/winter production, altitude
• 🌿 Biogas plants — plant name, output
• 🏙️ Energiestädte — municipalities with the Swiss "Energiestadt" label (score, year awarded, audits)
• 🏠 Solar roof potential — suitability category, area, orientation, and slope per roof segment
• 📊 Location energy profile — combines 5 layers into a single overview for any Swiss location
• 🗂️ SFOE dataset search — full-text search across SFOE publications on opendata.swiss
• ✅ Status check — verifies availability of both upstream APIs
• ☁️ Dual transport — stdio for Claude Desktop, Streamable HTTP for cloud deployment

Prerequisites

• Python 3.11+
• uv (recommended) or pip

Installation

Claude Desktop (stdio transport)

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "swiss-energy-mcp": {
      "command": "uvx",
      "args": ["swiss-energy-mcp"]
    }
  }
}

Config file locations:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Local development

git clone https://github.com/malkreide/swiss-energy-mcp.git
cd swiss-energy-mcp
uv sync
uv run swiss-energy-mcp

Cloud / HTTP transport (Streamable HTTP)

For use via claude.ai in the browser (e.g. on managed workstations without local software):

SWISS_ENERGY_TRANSPORT=http uvx swiss-energy-mcp

💡 "stdio for the developer laptop, HTTP for the browser."

Quickstart

Once connected in Claude Desktop, try:

What power plants are within 20 km of Bern?
Show me all wind turbines in the Jura region.
Is Zürich an Energiestadt? What's their score?
What is the solar potential of rooftops near lat=47.37, lon=8.54?
Give me a full energy profile for the region around Lucerne.
Find SFOE datasets about hydropower.

Available Tools

All tools accept WGS84 coordinates (lat/lon). Conversion to Swiss LV95 is handled internally.

Example Use Cases

→ More use cases by audience →

Data Sources

BFE Layers used:

• ch.bfe.elektrizitaetsproduktionsanlagen
• ch.bfe.windenergieanlagen
• ch.bfe.statistik-wasserkraftanlagen
• ch.bfe.photovoltaik-grossanlagen
• ch.bfe.biogasanlagen
• ch.bfe.energiestaedte
• ch.bfe.solarenergie-eignung-daecher

Configuration

All variables use the SWISS_ENERGY_ prefix and are validated at startup.

Both list-valued variables also accept a JSON array — ["https://a.test"] — in addition to the comma-separated form.

See .env.example for a template.

MCP Protocol Version

This server speaks two protocol eras over the same endpoint. The client's first request on a connection decides which one applies; a later claim from the other era is refused.

Both revisions are pinned in tests/test_protocol_version.py and asserted against the installed SDK, so a Dependabot bump of mcp cannot move either one silently. The handshake ceiling is measured against a live initialize through the assembled ASGI stack, not read off a constant name.

Note that the SDK's LATEST_PROTOCOL_VERSION is an alias for the modern era, not for the handshake era — pinning against it alone would leave the era that current clients actually negotiate free to drift.

Update policy. When the gate fails, do not edit the constant blindly: read the spec changelog between the two revisions, verify the server still behaves, then move the constant, this section, README.de.md and CHANGELOG.md together.

MCP Primitives

The server uses all three MCP primitives:

• Tools — 10 read-only tools (see above). Every search tool returns an EnergyResponse envelope: structured results plus a Markdown summary, explicit source / license attribution, and a match_type field.
• Resource — energy://layers, the static catalogue of BFE GeoAdmin layers.
• Prompt — energy_site_assessment, a guided location-analysis template.

Development Phase

The server is in Phase 1 (read-only). See docs/roadmap.md for the phased architecture and docs/security.md for the egress allow-list, SSRF protection and trifecta assessment.

Safety & Limits