Skip to main content
Glama
meteo-swiss-mcp

meteo-swiss-mcp

by cuolm

Swiss Weather MCP Server

Logo PyPI License Release Tests

A Model Context Protocol (MCP) server that provides AI applications with weather information for any place in Switzerland.

  • Forecasts for today and the next 8 days from the MeteoSwiss local forecasts, updated every hour

  • Measurements from about 160 SwissMetNet weather stations, updated every 10 minutes

  • Snow depth and new snow from MeteoSwiss and SLF stations and observers

  • Places on the Swiss national map, such as towns, districts, lakes and peaks, from swissNAMES3D

  • When the Sun and the Moon rise and set at a place, the civil twilight, the Moon's phase and how much of it is lit, calculated for any day

  • A bundled MCP client for testing

Data sources. This project is not an official MeteoSwiss product.

  • Weather forecasts and measurements: MeteoSwiss Open Data. Source: MeteoSwiss

  • Measurements of the IMIS mountain stations and the snow measured by observers: SLF, the WSL Institute for Snow and Avalanche Research, under CC BY 4.0. Source: SLF

  • Place names: swissNAMES3D. Source: Federal Office of Topography swisstopo

  • Municipalities and cantons: swissBOUNDARIES3D. Source: Federal Office of Topography swisstopo

Table of Contents

Related MCP server: wetter-mcp-server

Project Structure

swiss-weather-mcp/
├── src/swiss_weather_mcp/
│   ├── server.py           # MCP server and its tools
│   ├── places/             # swisstopo place lookup
│   ├── forecast/           # MeteoSwiss local forecasts
│   ├── measurements/       # MeteoSwiss SwissMetNet and SLF IMIS measurements
│   ├── astronomy/          # Sunrise, sunset, moonrise, moonset and phase
│   ├── downloads.py        # Downloads and caches files from data.geo.admin.ch and SLF
│   ├── distance.py         # Distance plus height gap, to choose a station for a place
│   ├── coordinates.py      # WGS84 latitude and longitude to LV95 and back
│   ├── formatting.py       # Times, wind directions and height differences in the answers
│   ├── errors.py           # The error for questions the data cannot answer
│   ├── log.py              # Logging setup
│   └── client.py           # MCP client
├── tests/swiss_weather_mcp/  # Tests
└── .github/workflows/      # CI and release pipelines

Installation

# As a command line tool
uv tool install swiss-weather-mcp

# With the optional MCP client, which pulls in the OpenAI SDK
uv tool install 'swiss-weather-mcp[client]'

# As a library dependency
uv add swiss-weather-mcp  # or: pip install swiss-weather-mcp

From source:

git clone https://github.com/cuolm/swiss-weather-mcp.git
cd swiss-weather-mcp
uv sync --extra client  # or, in a virtual environment: pip install -e ".[client]"

No configuration is needed, the server reads everything it requires from MeteoSwiss and swisstopo.

Usage

Running the Server

# stdio (default)
swiss-weather-mcp-server

# streamable-http
swiss-weather-mcp-server --transport=streamable-http --host=localhost --port=8050

From a source checkout, put uv run in front. --help lists all flags.

Where the server keeps its files, and --cache-all-forecast-points: see Cache and Downloads.

Running the Server with Docker

Images are built and published automatically by GitHub Actions to the project's GitHub Container Registry, tagged :latest (newest release) and by version.

# Published image
docker run -p 8050:8050 ghcr.io/cuolm/swiss-weather-mcp:latest

# Built from a source checkout
docker build -t swiss-weather-mcp .
docker run -p 8050:8050 swiss-weather-mcp

The server is then at http://localhost:8050/mcp/.

Each docker run starts a new container with an empty cache. Mount a volume to keep it, for example -v swiss-weather-cache:/root/.cache/swiss-weather-mcp.

Running the MCP Client

The bundled MCP client tests the server over stdio. It needs the client extra (see Installation) and starts the MCP server itself, but not the LLM, which has to be running first, for example in llama-server.

# Install llama.cpp, which provides llama-server, here with Homebrew on macOS or Linux
brew install llama.cpp

# Start llama-server with a model in its own terminal; it downloads the model on first use
llama-server --jinja --no-mmproj -hf unsloth/Qwen3.5-4B-GGUF --port 8080

# Run the client against it in a second terminal
swiss-weather-mcp-client --model=unsloth/Qwen3.5-4B-GGUF --base-url=http://localhost:8080/v1

From a source checkout, put uv run --extra client in front of the client. Other ways to install llama.cpp are in its installation guide.

--jinja uses the model's chat template, which tool calling needs (the default in current llama.cpp), and --no-mmproj skips the vision projector. --base-url is the server's OpenAI compatible API, and --model the name it lists under /v1/models.

Available Tools

Times are Swiss local time (see Times). Every tool with a location also takes an optional near, needed only when several places share the name (see Locations). Answers name the forecast point when it is not next to the place (see Forecast Points).

Tool

Answer

forecast_daily(location, start_date, days)

1 to 9 days: lowest and highest temperature, rain, weather with an emoji

forecast_rain(location, start, end)

Chance and amount of rain in 3-hour blocks

forecast_temperature(location, start, end)

Temperature hour by hour, or for one hour

forecast_sunshine(location, start, end)

Hours of sunshine over a period, or in one hour

forecast_wind(location, when)

Mean speed, gusts and direction

forecast_cloud_cover(location, when)

Total cloud cover and its low, medium and high layers

forecast_freezing_level(location, when)

Height of the 0 °C line

measurements_current(location)

What a station near the place measures now (see Measurements)

measurements_history(location, start_date, days)

1 to 366 past days: lowest, mean and highest temperature, rain, sunshine, strongest gust

measurements_snow(location)

Snow depth now, and new snow of the last 24 hours and 3 days (see Measurements)

measurements_extremes(extreme)

Where it is warmest, coldest, windiest, wettest or sunniest now

astronomy_sun(location, date)

Sunrise, sunset and civil twilight

astronomy_moon(location, date)

Moonrise, moonset, phase and how much is lit

current_date_and_time()

Today's weekday and the Swiss time now

Good to Know

Times

  • Times are Swiss clock time in ISO 8601, such as "2026-09-23T14:00". The server applies summer or winter time.

  • Answers give times with their UTC offset, such as 2026-09-23T13:00+02:00.

  • An hourly value stamped 14:00 covers 13:00 to 14:00. Cloud cover and the freezing level are values at that moment.

  • The forecast covers today and the next 8 days. current_date_and_time() gives today's date, which questions such as "tomorrow" or "tonight" need.

Locations

  • A location is a place name from swissNAMES3D: a town, village, city district, peak, pass, lake, glacier, valley or railway station, such as Zürich, Oerlikon, Titlis or Zürichsee.

  • Case and accents don't matter, and a few English names such as Geneva work too.

  • A name of several places, such as Blausee, needs near: a village next to the one the user means, such as near="Riederalp". Without it, the tool lists all places of the name, the biggest first, each with the call that chooses it and the municipality and canton it lies in:

    'Blausee' is the name of 6 places. [...] The biggest first:
      location="Blausee", near="Blausee-Mitholz": district and lake, fewer than 20 people, 887 m, municipality Kandergrund, canton Bern
      location="Blausee", near="Ramiswil": settlement, fewer than 20 people, 683 m, municipality Mümliswil-Ramiswil, canton Solothurn
      ...
  • The municipalities and cantons carry swisstopo's names, in the local language, such as Genève or Graubünden. They appear once the swissBOUNDARIES3D GeoPackage is downloaded in the background at start.

  • An unknown name gets up to 10 suggestions, such as Davos Dorf and Davos Platz for Davos.

Forecast Points

  • The forecast comes from a MeteoSwiss forecast point near the place. An answer names it in data_from when it is more than 1 km away or more than 50 m higher or lower.

  • Temperature changes faster with height than with distance: in the standard atmosphere (ISO 2533), air cools by 0.65 °C per 100 m.

  • So among the points within 5 km, the server takes the one with the smallest distance plus 20 times the height gap: 100 m of height gap counts like 2 km of distance. Without a point within 5 km, it takes the nearest one.

  • The factor 20 was tested on the real data: up to 20, the height gaps of lakes and peaks shrink a lot, and every town of 1,000 people or more still gets a point within 3 km.

Measurements

  • measurements_current uses one of the about 160 SwissMetNet stations: of the 3 with the smallest distance plus 20 times the height gap, the first that published a temperature in the last hour. Stations are far fewer than forecast points, so the station can still be far from the place and higher or lower.

  • Every answer starts with a sentence that says so, such as "The measurements for Braunwald (1290 m) are those of the MeteoSwiss station Elm (958 m), 13.5 km away and 332 m lower." As for the forecast points, a station at most 1 km away and 50 m higher or lower stands for the place, so it is not named.

  • It gives the temperature, humidity, dew point, rain and sunshine in the last 10 minutes, wind, gust, direction and sea-level pressure, plus the temperature and pressure change over the last 3 hours and the rain, sunshine and strongest gust of the last hour.

  • In the mountains it adds an slf_station block from one of the about 200 IMIS stations of the SLF, most between 1300 and 3300 m: the temperature, humidity, wind, direction and strongest 5-second gust of the 30 minutes up to its latest row. It is added only when the station's distance plus 20 times the height gap is smaller than the MeteoSwiss station's, and the station published a temperature in the last hour (of the 3 best, the first that did). On the real data that is no place below 800 m and most places above 2000 m. Its own data_from names the station, its distance and height. When SLF cannot be reached, the answer comes without the block.

  • measurements_history gives MeteoSwiss's daily values of the station chosen the same way: of the 3 first stations, the first with a temperature on the days asked. A day runs from 00:00 to 24:00 UTC, which is 01:00 to 01:00 Swiss time in winter and 02:00 to 02:00 in summer, and MeteoSwiss publishes it the next morning. The days go back to when the station started, such as 1864 for Zürich / Fluntern, where the rain from 0 to 0 UTC and the gust start in 1981; a value the station did not measure is None. Days before this year come from a file of up to about 6.4 MB per station.

  • measurements_snow gives the snow depth and the new snow, each from its own station: of the 3 with the smallest distance plus 20 times the height gap, the first with a current value. Each has its own data_from, which names the station, its distance and height, unless the station is next to the place.

    • The snow depth comes from one of about 75 MeteoSwiss stations, one of about 130 automatic SLF stations or one of about 100 SLF manual measuring sites, where an observer measures the snow by hand each morning from November to April. A depth measured every 10 or 30 minutes counts for 210 minutes, as on SLF's map; an observer's counts until the next morning.

    • The new snow comes only from SLF: measured by an observer, or, at an automatic station, calculated by SLF from the snow depth, as old snow settles while new snow falls. Both cover the 24 hours up to about 06:00 UTC. The 3 days are the sum of three 24-hour values, as SLF adds them for its maps.

    • SLF says the observers' values are very accurate, but that most manual sites lie below about 2000 m, so with moist snow or rain more new snow lies higher up.

    • Only stations within 25 km by distance plus 20 times the height gap are used, such as 15 km away and 500 m higher, as snow changes with height and terrain. Tested on the 5817 forecast points: 94 % of those between 1200 and 2000 m keep a new snow station; below 800 m, where the nearest SLF station is often 40 km away and 600 m higher, 88 % get none, but 96 % still get a snow depth.

    • A block is null when none of its stations has a current value, and the tool says so when both are.

  • measurements_extremes lists the first 5 stations by temperature or gust. For the wettest, it lists the first 5 rainy stations and counts the rainy stations in Switzerland and in each canton.

  • For the sunniest it groups the stations by their sun in the last 10 minutes with the sunshine terms of MeteoSwiss: mostly sunny (8 to 10 minutes, 80 to 100 %), rather sunny (5 to 7), partly sunny (2 to 4), only a little sunshine (1) and hardly any sunshine (0). MeteoSwiss's ranges meet at 20, 50 and 80 %; a station exactly there counts for the sunnier term, so 2 minutes (20 %) is partly sunny. The cantons come in the order of their stations' average sun.

Forecast Values Are Medians

  • Temperature and rain are the median of the many possible outcomes MeteoSwiss calculates, not the most likely value.

  • Medians do not add up: when showers are possible but unlikely in any 3-hour block, every block shows 0 mm while the day's median is above 0.

  • forecast_daily gives the rain of a day, and forecast_rain the chance and how much a wet hour may bring.

Cache and Downloads

  • The cache lives in your OS cache directory, such as ~/Library/Caches/swiss-weather-mcp on macOS or ~/.cache/swiss-weather-mcp on Linux. SWISS_WEATHER_MCP_CACHE_DIR moves it elsewhere.

  • The first start downloads the swissNAMES3D archive (about 33 MB) and the swissBOUNDARIES3D GeoPackage (about 37 MB, kept unpacked at about 74 MB).

  • MeteoSwiss publishes a new forecast run every hour, each hourly parameter as one file of about 30 to 34 MB for all forecast points. By default the server downloads such a file for every new forecast point and keeps only that point's rows.

  • With --cache-all-forecast-points it keeps the whole files, so further places in the same run need no new download. This helps when many places are asked within the hour, at the cost of disk space.

Example Usage with LMStudio

Using the streamable-http transport layer

Configure the mcp.json file in LMStudio:

{
  "mcpServers": {
    "swiss_weather_mcp_server": {
      "url": "http://localhost:8050/mcp/"
    }
  }
}

Run the MCP server with the streamable-http transport, as in Running the Server.

Using the stdio transport layer

Configure the mcp.json file in LMStudio. Replace <path-to> so the command is the full path that which swiss-weather-mcp-server prints:

{
  "mcpServers": {
    "swiss_weather_mcp_server": {
      "command": "<path-to>/swiss-weather-mcp-server"
    }
  }
}

LMStudioMCPServer

Resources

License

Licensed under the Apache License 2.0.

Available Tools

12 tools
astronomy_moonA
Read-only
        Get when the Moon rises and sets at a place on a day, its phase and how much of it is lit.

        Use this for "when does the moon rise tonight" or "how full is the moon tonight". The
        times are for a level horizon, so in a valley the Moon appears later behind the
        mountains. The day has a moon_phase_time when New Moon, First Quarter, Full Moon or Last
        Quarter happens on it. The lit percent is the one at 12:00.

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".
            date (str): The day, e.g. "2026-09-23".

        Returns:
            dict: The place, the date, the moonrise and moonset, None when the Moon does not rise
                or set that day, the phase with its emoji and time, and the lit percent.

        Examples:
            astronomy_moon("Zürich", "2026-09-23")
        

Inputs: date (required), location (required), near.

astronomy_sunA
Read-only
        Get when the Sun rises and sets at a place on a day, and when civil twilight begins and ends.

        Use this for "when does the sun rise tomorrow" or "until when is it light tonight". Civil
        twilight is the light before sunrise and after sunset; outside it, artificial light is
        normally needed outdoors. The times are for a level horizon, so in a valley the Sun
        appears later behind the mountains.

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".
            date (str): The day, e.g. "2026-09-23".

        Returns:
            dict: The place, the date, the begin of civil twilight, sunrise, sunset and the end of
                civil twilight.

        Examples:
            astronomy_sun("Zürich", "2026-09-23")
        

Inputs: date (required), location (required), near.

current_date_and_timeA
Read-only
        Get the current weekday and Swiss local time.

        Call this first when the question is relative, such as "tomorrow" or "tonight", because
        the forecast tools take a real date rather than an offset. The time is written the way
        the tools read it, ISO 8601 without an offset, so it can be sent back to them as it is.

        Returns:
            str: For example "Today is Wednesday, 2026-09-23T13:02 (Swiss time)".
        

Inputs: no named parameters. Returns: result

forecast_cloud_coverA
Read-only
        Get how cloudy it is at a place at a specific time.

        Use this for "how cloudy is it at 14:00". MeteoSwiss publishes low, medium and high
        cloud separately, and they overlap, so the total is an estimate that assumes the layers
        are independent. All three layers are returned as well, so low cloud such as fog can be
        told apart from high cloud.

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".
            when (str): A full hour, e.g. "2026-09-23T14:00". Today or up to 8 days ahead.

        Returns:
            dict: data_from when the forecast point is far away or at a significantly different
                height, the place, the total cloud cover and its low, medium and high layers in
                percent, the time it is valid for and the model run.

        Examples:
            forecast_cloud_cover("Zürich", "2026-09-23T14:00")
        

Inputs: when (required), location (required), near.

forecast_dailyA
Read-only
        Get the whole-day forecast at a place, for one day or several days in a row.

        Use this for "how is the weather tomorrow" or "how is the weather at the weekend", and
        for the total rain of a day. Each day covers a Swiss calendar day, 00:00 to 24:00 local
        time. The minimum and maximum are the lowest and highest hourly mean temperature of
        that day, and the weather words describe the daytime.

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".
            start_date (str): The first day, e.g. "2026-09-23". Today or up to 8 days ahead.
            days (int): How many days in a row, from 1 to 9. Default 1.

        Returns:
            dict: data_from when the forecast point is far away or at a significantly different
                height, the place, one row per day and the model run. In 8 of 10 possible outcomes,
                the day's rain lies between its 10th and 90th percentile. A value is None when
                MeteoSwiss does not publish it for the place.

        Examples:
            forecast_daily("Zürich", "2026-09-23")
            forecast_daily("Zürich", "2026-09-26", 2)   # a weekend
        

Inputs: location (required), start_date (required), days, near.

forecast_freezing_levelA
Read-only
        Get the freezing level, the height of the 0 °C line, at a place at a specific time.

        Use this for "how high is the freezing level at 14:00".

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".
            when (str): A full hour, e.g. "2026-09-23T14:00". Today or up to 8 days ahead.

        Returns:
            dict: data_from when the forecast point is far away or at a significantly different
                height, the place, the freezing level in metres above sea level, the time it is
                valid for and the model run.

        Examples:
            forecast_freezing_level("Zürich", "2026-09-23T14:00")
        

Inputs: when (required), location (required), near.

forecast_rainA
Read-only
        Get when and how much it may rain at a place, and the weather in words, in 3-hour blocks
        over a period.

        Use this for "will it rain at 15:00" or "how is the weather this afternoon". Each block
        covers the 3 hours between its from and to times
        and gives the chance of rain, the median rainfall, how much the wettest hour may bring
        (its 90th percentile) and the weather in words. The median is often 0 when showers are
        possible, so read the chance and the "up to" amount as well. A period up to the end of
        the forecast ends with its last full 3-hour block. Medians do not add up, so for the
        total rain of a whole day use forecast_daily.

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".
            start (str): Start of the period, a full hour, e.g. "2026-09-23T12:00". Today or up to 8 days ahead.
            end (str): End of the period, a full hour after start, e.g. "2026-09-23T18:00".

        Returns:
            dict: data_from when the forecast point is far away or at a significantly different
                height, the place, one row per 3-hour block and the model run.

        Examples:
            forecast_rain("Zürich", "2026-09-23T15:00", "2026-09-23T18:00")    # 15:00
            forecast_rain("Zürich", "2026-09-23T12:00", "2026-09-23T18:00")    # the afternoon
        

Inputs: end (required), start (required), location (required), near.

forecast_sunshineA
Read-only
        Get the sunshine hours at a place over a period.

        Use this for "how sunny is it at 15:00" or "how sunny is it this afternoon". Without end
        it returns the one hour starting at start.

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".
            start (str): Start of the period, a full hour, e.g. "2026-09-23T06:00". Today or up to 8 days ahead.
            end (str): Optional. End of the period, a full hour after start, e.g. "2026-09-23T18:00".

        Returns:
            dict: data_from when the forecast point is far away or at a significantly different
                height, the place, the sunshine in hours, the period and the model run.

        Examples:
            forecast_sunshine("Zürich", "2026-09-23T15:00")                        # one hour
            forecast_sunshine("Zürich", "2026-09-23T12:00", "2026-09-23T18:00")    # the afternoon
        

Inputs: start (required), location (required), end, near.

forecast_temperatureA
Read-only
        Get the temperature hour by hour at a place, with its likely range.

        Use this for "how warm is it at 15:00" or "how warm is it this afternoon". Without end
        it returns the one hour starting at start. Each row gives the mean temperature of one
        hour, between its from and to times.

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".
            start (str): Start of the period, a full hour, e.g. "2026-09-23T15:00". Today or up to 8 days ahead.
            end (str): Optional. End of the period, a full hour after start, e.g. "2026-09-23T18:00".

        Returns:
            dict: data_from when the forecast point is far away or at a significantly different
                height, the place, one row per hour and the model run. In 8 of 10 possible outcomes,
                the temperature lies between its 10th and 90th percentile.

        Examples:
            forecast_temperature("Zürich", "2026-09-23T15:00")                        # one hour
            forecast_temperature("Zürich", "2026-09-23T12:00", "2026-09-23T18:00")    # the afternoon
        

Inputs: start (required), location (required), end, near.

forecast_windA
Read-only
        Get the wind at a place at a specific time: mean speed, strongest gust and direction.

        Use this for "how windy is it at 14:00". The speed is the mean over the hour up to that
        time, and the gust the strongest one-second gust in that hour. In 9 of 10 possible
        outcomes the gust stays below its 90th percentile, so the percentile is a cautious high
        estimate, not the highest gust possible. The direction is where the wind blows from, in
        degrees clockwise from north (0 is a north wind, 180 a south wind) and as a compass
        point.

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".
            when (str): A full hour, e.g. "2026-09-23T14:00". Today or up to 8 days ahead.

        Returns:
            dict: data_from when the forecast point is far away or at a significantly different
                height, the place, the wind, the time it is valid for and the model run.

        Examples:
            forecast_wind("Zürich", "2026-09-23T14:00")
        

Inputs: when (required), location (required), near.

measurements_currentA
Read-only
        Get the latest measurements of a MeteoSwiss station near a place.

        Use this for "how warm is it now" or "is it raining now". The values are those of the
        station named in data_from. MeteoSwiss publishes new values about every 10 minutes.

        Args:
            location (str): Name of a place in Switzerland, e.g. "Zürich".

        Returns:
            dict: data_from, the place, the time of the measurements and the measured values. A
                value is None when the station has not published it.

        Examples:
            measurements_current("Zürich")
        

Inputs: location (required), near.

measurements_extremesA
Read-only
        Get where in Switzerland it is warmest, coldest, windiest, wettest or sunniest now.

        Use this for "where is it warmest now" or "where is it sunny now". The values are those
        of about 160 MeteoSwiss stations, so give the altitude with each station. For the
        sunniest, the stations are grouped by their sun in the last 10 minutes with MeteoSwiss's
        sunshine terms: mostly sunny (8 to 10 minutes), rather sunny (5 to 7), partly sunny (2 to
        4), only a little sunshine (1) and hardly any sunshine (0). The cantons come in order of
        their stations' average sun, sunniest first. A station is rainy when it had rain in the
        last 10 minutes.

        Args:
            extreme (str): One of "warmest", "coldest", "windiest", "wettest" or "sunniest".

        Returns:
            dict: The time of the measurements and the first 5 stations. For the sunniest instead
                the number of stations in each sunshine group, in Switzerland and in each canton,
                the sunniest canton first. For the wettest also the number of rainy stations out of
                those that measure rain, in Switzerland and in each canton.

        Examples:
            measurements_extremes("warmest")
        

Inputs: extreme (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 12 tools

    Disambiguation4/5

    Each tool targets a distinct quantity (rain, temperature, sunshine, wind, cloud, freezing level), and the descriptions explicitly steer between them, e.g. telling the agent to use forecast_daily for a whole-day rain total rather than summing forecast_rain medians. The only residual overlap is that broad questions like 'how is the weather this afternoon' could plausibly hit forecast_rain, forecast_temperature or forecast_sunshine, since rain also returns weather words.

    Naming Consistency4/5

    Names follow a clean namespace_variable snake_case pattern grouped into measurements_*, forecast_* and astronomy_* families. The single outlier is current_date_and_time, which breaks the prefix convention and is a long name with no matching group, but it is still readable and unambiguous.

    Tool Count5/5

    Twelve tools is well within the sweet spot, and each earns its place as a discrete weather variable or reference utility. Nothing appears redundant or padded; splitting forecast variables per quantity keeps each call simple.

    Completeness4/5

    The surface covers current observations, hourly/daily forecasts, extremes, sun/moon astronomy and a time anchor for relative questions, which is strong lifecycle coverage for a weather server. Gaps exist for humidity, pressure, visibility, UV and snow, and there is no station search/list tool, though the location-name argument means agents can mostly work around these.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI models to access Swiss weather and climate data from MeteoSwiss, including current observations, forecasts, and warnings.
      6
      33 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for querying MeteoSwiss open weather data, providing access to station data, forecasts, radar composites, and more via natural language.
      210 PyPI
      46
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time weather forecasts, current conditions, and smart umbrella recommendations through MCP tools, backed by the Open-Meteo API.
      -