Swiss Energy Mcp
Give your agent Swiss-wide energy datasets from SFOE/BFE plus GeoAdmin REST so maps, permits, and infrastructure layers ship with correct federal geometry and energy stats.
Overview
io.github.malkreide/swiss-energy-mcp is a MCP server for the Build phase that connects agents to Swiss SFOE/BFE energy REST APIs and GeoAdmin geospatial REST endpoints.
What is this MCP server?
- Swiss energy data via SFOE and BFE REST APIs in one MCP surface
- GeoAdmin REST integration for geospatial layers alongside energy metrics
- Broader coverage than electricity-only server for multi-source energy dashboards
- PyPI uvx stdio package at version 0.3.3
- Energy & Infrastructure registry category for map-heavy Swiss cleantech builds
- Package version 0.3.3, stdio transport, PyPI registry via uvx
- Dual upstream families: SFOE/BFE energy REST and GeoAdmin REST
- Registry category Energy & Infrastructure, publisher scope core
What problem does it solve?
Energy and map features for Switzerland stall when you must juggle separate SFOE, BFE, and GeoAdmin docs while the agent cannot call them natively.
Who is it for?
Developers building Swiss cleantech, geospatial energy, or infrastructure dashboards who need SFOE, BFE, and GeoAdmin in one MCP during implementation.
Skip if: Simple household bill calculators that only need ElCom tariffs, or products outside Switzerland with no GeoAdmin dependency.
What do I get? / Deliverables
After registration, your agent can query combined energy and GeoAdmin sources so integration code, map layers, and data models align with federal APIs.
- Unified agent access to SFOE/BFE energy REST and GeoAdmin REST
- Integration patterns for map-backed Swiss energy features
- Stdio MCP setup suitable for local dev and agent-driven codegen
Recommended MCP Servers
Journey fit
Canonical shelf is Build because SFOE, BFE, and GeoAdmin calls belong in the integration layer of energy or geospatial products you are actively coding. Integrations fits combined energy statistics and GeoAdmin spatial layers that backend routes and map components must consume reliably.
How it compares
Multi-agency Swiss energy plus GeoAdmin MCP hub, not a single-tariff electricity-only connector.
Common Questions / FAQ
Who is io.github.malkreide/swiss-energy-mcp for?
Solo builders shipping Swiss energy or map products who want one MCP server for SFOE, BFE, and GeoAdmin REST instead of hand-rolled fetch scripts.
When should I use io.github.malkreide/swiss-energy-mcp?
Use it while building backend integrations and map layers that must combine federal energy statistics with GeoAdmin spatial services.
How do I add io.github.malkreide/swiss-energy-mcp to my agent?
Install via uvx swiss-energy-mcp, register the stdio MCP server in Claude Code or Cursor, and exercise energy plus GeoAdmin tools before merging map-related PRs.