io.github.malkreide/swiss-energy-mcp

Registre officiel Autres

Swiss energy data via SFOE/BFE and GeoAdmin REST APIs

Que pouvez-vous faire avec io.github.malkreide/swiss-energy-mcp ?

  • 🔍 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

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

PYPI package swiss-energy-mcp
Claude Code
claude mcp add swiss-energy-mcp -- uvx swiss-energy-mcp==0.5.1
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "swiss-energy-mcp": {
            "command": "uvx",
            "args": [
                "swiss-energy-mcp==0.5.1"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. ⚡ swiss-energy-mcp
  2. Overview
  3. Features
  4. Prerequisites
  5. Installation
  6. Quickstart
  7. Available Tools
  8. Data Sources
  9. Configuration
  10. MCP Protocol Version
  11. MCP Primitives
  12. Development Phase
  13. Safety & Limits
  14. Architecture
  15. Project Structure
  16. Known Limitations
  17. Testing
  18. Changelog
  19. Contributing
  20. Security
  21. License
  22. Author
  23. Credits & Related Projects
  24. Installation

🇨🇭 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

ToolDescription
energy_find_power_plantsAll electricity generation plants within a radius (optional category filter)
energy_find_wind_turbinesWind turbines with manufacturer, model, hub height
energy_find_hydro_plantsHydropower plants with capacity and expected output
energy_find_pv_installationsLarge PV installations with annual/winter production
energy_find_biogas_plantsBiogas plants
energy_find_energy_citiesMunicipalities with "Energiestadt" label
energy_solar_potentialSolar suitability of roof segments at a location
energy_location_profileCombined energy profile (5 layers) for a location
energy_search_bfe_datasetsFull-text search over SFOE datasets on opendata.swiss
energy_check_statusCheck availability of GeoAdmin and opendata.swiss APIs

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

Example Use Cases
QueryTool
"Power plants near Bern (20 km radius)?"energy_find_power_plants
"Wind turbines in the Jura?"energy_find_wind_turbines
"Is Zürich an Energiestadt?"energy_find_energy_cities
"Solar potential of rooftops near lat=47.37, lon=8.54?"energy_solar_potential
"Full energy profile for Lucerne region?"energy_location_profile
"SFOE datasets on hydropower?"energy_search_bfe_datasets

→ More use cases by audience →


Data Sources

SourceURLAuth
GeoAdmin REST API (swisstopo)api3.geo.admin.chNone
opendata.swiss CKAN APIopendata.swiss/api/3/actionNone

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.

Environment variableDefaultDescription
SWISS_ENERGY_TRANSPORTstdioTransport mode: stdio or http
SWISS_ENERGY_HOST127.0.0.1Host for HTTP transport. Bind 0.0.0.0 only inside a container.
SWISS_ENERGY_PORT8000Port for HTTP transport
SWISS_ENERGY_CORS_ORIGINShttps://claude.aiComma-separated allowed CORS origins (HTTP transport)
SWISS_ENERGY_ALLOWED_HOSTS(empty)Comma-separated inbound Host allow-list. Only needed for a non-loopback bind.
SWISS_ENERGY_LOG_LEVELINFOLog level: DEBUG / INFO / WARNING / ERROR
SWISS_ENERGY_HTTP_TIMEOUT20Upstream HTTP timeout in seconds

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.

EraRevisionWho reaches it
initialize handshake2024-11-05 … 2025-11-25What today's clients speak. The server answers with the revision asked for, or with the 2025-11-25 ceiling when the request asks for something newer.
Per-request envelope2026-07-28A request carrying the 2026-07-28 _meta envelope opens a modern connection.

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.

Server identity

Every modern-era response carries the server's identity under _meta["io.modelcontextprotocol/serverInfo"]; the handshake era carries the same block once, in initialize.serverInfo:

{
  "name": "swiss_energy_mcp",
  "title": "Swiss Energy MCP",
  "version": "<version from the package metadata>",
  "websiteUrl": "https://github.com/malkreide/swiss-energy-mcp"
}

version comes from the installed package metadata, never from a literal in src/ — scripts/check_version_sync.py rejects a hand-maintained number there. Both eras are measured through the assembled ASGI stack in tests/test_server_identity.py: the SDK default for version is the empty string, so a missing constructor argument is silent rather than red.

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

AspectDetails
AccessRead-only (readOnlyHint: true) — the server cannot modify or delete any data
Personal dataNo personal data — all sources are aggregated, public infrastructure data
Rate limitsBuilt-in per-query caps (max 50 search results, default 5 km radius)
Timeout20 seconds per API call
AuthenticationNo API keys required — both APIs are publicly accessible
LicensesAll data under open licenses via opendata.swiss (OGD)
Terms of ServiceSubject to ToS of the respective data sources: GeoAdmin, opendata.swiss, SFOE/BFE

Architecture

┌─────────────────┐     ┌───────────────────────────┐     ┌──────────────────────────┐
│   Claude / AI   │────▶│   Swiss Energy MCP        │────▶│  SFOE / BFE Open Data    │
│   (MCP Host)    │◀────│   (MCP Server)            │◀────│                          │
└─────────────────┘     │                           │     │  GeoAdmin REST API       │
                        │  10 Tools                 │     │  (api3.geo.admin.ch)     │
                        │  Stdio | HTTP             │     │                          │
                        │                           │     │  opendata.swiss CKAN     │
                        │  server.py (FastMCP)      │     │  (opendata.swiss)        │
                        │  api_client.py            │     └──────────────────────────┘
                        │   LV95 conversion         │
                        │   GeoAdmin queries        │
                        └───────────────────────────┘
Infrastructure Components
ComponentMetaphorFunction
api_client.pySwitchboardHandles HTTP requests, coordinate conversion, error handling
LV95 converterTranslatorConverts WGS84 (lat/lon) to Swiss coordinate system
server.pyStorefrontExposes all 10 tools via FastMCP

Project Structure

swiss-energy-mcp/
├── src/
│   └── swiss_energy_mcp/
│       ├── server.py          # FastMCP setup, lifespan, entry point
│       ├── settings.py        # Typed configuration (pydantic-settings)
│       ├── logging_config.py  # Structured JSON logging to stderr
│       ├── api_client.py      # HTTP client, egress guard, LV95 conversion
│       ├── models.py          # Pydantic input/output models
│       ├── formatting.py      # Markdown summary builders
│       ├── resources.py       # Layer-catalogue resource + prompt
│       └── tools/             # One module per tool group
│           ├── installations.py   # power, wind, hydro, PV, biogas
│           ├── places.py          # solar, Energiestadt, location profile
│           └── catalog.py         # dataset search, status
├── tests/
│   ├── test_unit.py         # Pure-unit tests (coords, formatting, egress)
│   ├── test_tools.py        # Tool tests with respx-mocked APIs
│   └── test_live.py         # Live integration tests (marked `live`)
├── docs/                    # roadmap.md, security.md
├── Dockerfile               # Multi-stage build, non-root user
├── pyproject.toml
├── CHANGELOG.md
├── CONTRIBUTING.md          # Contribution guide (English)
├── CONTRIBUTING.de.md       # Contribution guide (German)
├── SECURITY.md              # Security policy (English)
├── SECURITY.de.md           # Security policy (German)
├── LICENSE
├── README.md                # This file (English)
└── README.de.md             # German version

Known Limitations

  • GeoAdmin radius search: Maximum search radius depends on layer density; very large radii may return partial results
  • Solar potential: Layer ch.bfe.solarenergie-eignung-daecher covers building footprints — not all roof types are classified
  • Energiestadt: Only municipalities with active label are included; historical entries may be incomplete
  • opendata.swiss CKAN: Full-text search covers metadata only, not document contents

Testing

# Unit tests (no API key required)
PYTHONPATH=src pytest tests/ -m "not live"

# Live integration tests (network access required)
PYTHONPATH=src pytest tests/ -m "live"

Changelog

See CHANGELOG.md


Contributing

See CONTRIBUTING.md (🇩🇪 Deutsch)


Security

See SECURITY.md (🇩🇪 Deutsch) for the security policy and posture summary, and docs/security.md for the full technical security model.


License

MIT License — see LICENSE


Author

Hayal Oezkan · malkreide


Installation

Run via uv's uvx — no clone or manual install needed. Add to your MCP client config (mcpServers for Claude Desktop, Cursor and Windsurf; use a top-level servers key for VS Code in .vscode/mcp.json):

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

Questions fréquentes

Qu'est-ce que io.github.malkreide/swiss-energy-mcp ?

Swiss energy data via SFOE/BFE and GeoAdmin REST APIs

Comment installer io.github.malkreide/swiss-energy-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add swiss-energy-mcp -- uvx swiss-energy-mcp==0.5.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.malkreide/swiss-energy-mcp ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.malkreide/swiss-energy-mcp est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.malkreide/swiss-energy-mcp ?

Il est publié par malkreide. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.