Swiss Energy MCP vs Swiss Environment MCP
A side-by-side look at the Swiss Energy MCP and Swiss Environment MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Swiss Energy MCP for environment & nature work as a local process; choose Swiss Environment MCP for environment & nature as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Swiss Energy MCP when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SWISS_ENERGY_TRANSPORT, SWISS_ENERGY_HOST, SWISS_ENERGY_PORT, SWISS_ENERGY_CORS_ORIGINS, SWISS_ENERGY_ALLOWED_HOSTS, SWISS_ENERGY_LOG_LEVEL, SWISS_ENERGY_HTTP_TIMEOUT. - You want tools like
energy_find_power_plants, energy_find_wind_turbines, energy_find_hydro_plants.
Choose Swiss Environment MCP when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You want tools like
env_nabel_stations, env_nabel_current, env_air_limits_check.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 49/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SWISS_ENERGY_TRANSPORTSWISS_ENERGY_HOSTSWISS_ENERGY_PORTSWISS_ENERGY_CORS_ORIGINSSWISS_ENERGY_ALLOWED_HOSTSSWISS_ENERGY_LOG_LEVELSWISS_ENERGY_HTTP_TIMEOUT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 10 | 21 |
| Full listing | View Swiss Energy MCP | View Swiss Environment MCP |
Tools & capabilities
Swiss Energy MCP tools 10
energy_find_power_plantsAll electricity generation plants within a radius (optional category filter)energy_find_wind_turbinesWind turbines with manufacturer, model, hub heightenergy_find_hydro_plantsHydropower plants with capacity and expected outputenergy_find_pv_installationsLarge PV installations with annual/winter productionenergy_find_biogas_plantsBiogas plantsenergy_find_energy_citiesMunicipalities with "Energiestadt" labelenergy_solar_potentialSolar suitability of roof segments at a locationenergy_location_profileCombined energy profile (5 layers) for a locationenergy_search_bfe_datasetsFull-text search over SFOE datasets on opendata.swissenergy_check_statusCheck availability of GeoAdmin and opendata.swiss APIs
Swiss Environment MCP tools 21
env_nabel_stationsList all 16 NABEL monitoring stations with location type and cantonenv_nabel_currentCurrent air quality data for a station (NO₂, O₃, PM10, PM2.5, SO₂, CO)env_air_limits_checkCompare a measurement against Swiss LRV limits and WHO 2021 guidelinesenv_hydro_stationsFilter hydrological gauging stations by water body (canton filter unavailable — see notes)env_hydro_currentCurrent water level, flow rate and temperature at a stationenv_hydro_historyLatest LINDAS value plus the access path for real time series ⚠️env_flood_warningsActive flood warnings filtered by danger level (nationwide — canton filter not applied)env_bathing_waterBathing water quality (E.coli, enterococci) per bathing site — multi-year time seriesenv_hazard_overviewRouter: points to the dedicated live hazard tools + official portals (no network call — the aggregate `naturgefahren.ch` API was discontinued)env_hazard_regionsRouter: maps a hazard type (flood/avalanche/wildfire/snow) to the right live tool + portal (no network call)env_wildfire_dangerWildfire danger index by canton and regionenv_snow_stationsList automatic SLF/IMIS snow measurement stations (by canton)- +9 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Swiss Energy MCP
{
"mcpServers": {
"swiss-energy-mcp": {
"command": "uvx",
"args": [
"swiss-energy-mcp"
],
"env": {
"SWISS_ENERGY_TRANSPORT": "YOUR_SWISS_ENERGY_TRANSPORT_HERE",
"SWISS_ENERGY_HOST": "YOUR_SWISS_ENERGY_HOST_HERE",
"SWISS_ENERGY_PORT": "YOUR_SWISS_ENERGY_PORT_HERE",
"SWISS_ENERGY_CORS_ORIGINS": "YOUR_SWISS_ENERGY_CORS_ORIGINS_HERE",
"SWISS_ENERGY_ALLOWED_HOSTS": "YOUR_SWISS_ENERGY_ALLOWED_HOSTS_HERE",
"SWISS_ENERGY_LOG_LEVEL": "YOUR_SWISS_ENERGY_LOG_LEVEL_HERE",
"SWISS_ENERGY_HTTP_TIMEOUT": "YOUR_SWISS_ENERGY_HTTP_TIMEOUT_HERE"
}
}
}
}
Swiss Environment MCP
{
"mcpServers": {
"swiss-environment-mcp": {
"command": "uvx",
"args": [
"swiss-environment-mcp"
]
}
}
}
Frequently asked questions
Swiss Energy MCP is categorized under Environment & Nature and uses a local stdio subprocess. Swiss Environment MCP belongs to Environment & Nature and uses a local stdio subprocess. Pick Swiss Energy MCP for environment & nature work and Swiss Environment MCP for environment & nature.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Swiss Energy MCP has no declared pricing — check the project's own site. Swiss Environment MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add swiss-energy-mcp and swiss-environment-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Swiss Energy MCP has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Swiss Environment MCP has 49/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.