Skip to main content
Glama
Sign In
gios-air-mcp

gios-air-mcp

by bartosz-kuc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to gios-air-mcp

No user-submitted related servers found.

    Related Servers

    • powietrze-mcp

      ContentWriterco
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to check live air quality in Poland, including the nearest official GIOŚ monitoring stations with the air quality index and hourly PM2.5, PM10, NO2, O3 and SO2 readings, plus smog warnings for the voivodeship and a 3-day Copernicus CAMS forecast of particulate matter and pollen. Can be used via a public no-key endpoint or run locally.
      3
      395 npm
      MIT

    • airly

      jsynowiec
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language interaction with air quality data from Airly, including real-time measurements, nearby stations, and forecasts.
      226 npm
      MIT

    • airkorea-realtime-mcp

      hlucent
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying real-time air quality measurements, integrated air quality index (CAI), and monitoring station information from Korea's Air Korea OpenAPI, including station search and nearby station lookup.
      MIT

    • mcp-openaq

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying global air-quality data from the OpenAQ API, including nearest-station readings, station discovery, latest pollutant values, and historical time series for sensors.
      657 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: stations, sensors, readings, and air index. There is no overlap, and an agent can easily determine which tool to call for a given query.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_stations, get_station_sensors, get_sensor_readings, get_air_index). The naming is uniform, predictable, and uses clear, specific verbs.

    Tool Count5/5

    With exactly 4 tools, the server is tightly scoped to air quality monitoring without redundancy. Each tool covers a necessary step in the workflow, making the count ideal for the domain.

    Completeness4/5

    The tool surface covers the full core workflow: discover stations, inspect sensors, fetch readings, and get an aggregated index. Minor gaps include lack of historical readings beyond 24 hours and no station metadata endpoint, but these are acceptable for a minimal yet functional set.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources