uba-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Unofficial read-only MCP server for UBA air quality — the Umweltbundesamt (German Federal Environment Agency) Air Data API v4. Hourly measurements from ~400 German measuring stations (PM10, PM2.5, NO2, O3, SO2, CO, benzene ...) since 2016, with the official UBA air-quality index (LQI, 2025 revision: very good / good / moderate / poor / very poor) per pollutant and per hour. Stations are found by code (e.g. DEBE010 = Berlin Wedding), numeric id, or city name. All times are CET/CEST as returned by the API. Built by Mohammad Abbasi (mohammad-abbasi-sh) — https://almanibama.ir · https://mabbasi.ir — Germany MCP factory.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| uba_list_stationsA | List German air-quality measuring stations, filterable by city, state (network code like BE or name like Berlin), type (background / traffic / industry), area (urban / suburban / rural) or a name/code substring. limit: 1..100 (default 20). |
| uba_station_detailA | Full detail of one measuring station: code, name, city, address, coordinates, type, area, network, active period, data availability window, and which pollutants have recent data. station: code (DEBE010), numeric id, or city name. |
| uba_current_air_qualityA | Latest hourly air quality at a station: each pollutant's value (µg/m³) with the UBA air-quality index class (very good / good / moderate / poor / very poor) and the overall index for that hour. station: code (DEBE010), numeric id, or city name. |
| uba_measurementsA | Hourly air-quality values for a station over a date range (max 31 days), with per-pollutant min/max/mean and daily means. component: one pollutant code (PM10, PM2, NO2, O3, SO2, CO ...) to limit the series to it; empty = all pollutants the station measures. station: code (DEBE010), numeric id, or city name. |
| uba_list_componentsB | All pollutants UBA publishes air-quality data for: code, symbol, unit and name (PM10, PM2.5, NO2, O3, SO2, CO, benzene, lead ...). |
| uba_list_networksB | The measuring networks behind the stations: one per Bundesland (16) plus the UBA's own network. |
| uba_healthA | Check whether the UBA Air Data API is reachable right now. Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct resource or action: listing stations/components/networks, station detail, current snapshot, historical series, and connectivity check. The only mild overlap is uba_current_air_quality vs uba_measurements, but the descriptions make the 'latest hour' vs 'date range with aggregates' distinction clear.
All names share the uba_ prefix, which makes the family instantly recognizable. The verb style is not strictly uniform (list_* verbs mixed with noun-only names like uba_station_detail, uba_measurements, uba_health), but the pattern remains readable and predictable by resource.
Seven tools is well-scoped for a read-only wrapper around the UBA Air Data API. Every tool earns its place: discovery (stations, components, networks), retrieval (detail, current, measurements) and a diagnostic health probe.
The read-only surface covers discovery, detail, current values, historical measurements and API health, with no obvious dead ends for the stated purpose. Minor gaps exist—no cross-station pollutant search or way to fetch the index-class definitions themselves—but agents can work around these via the existing tools.