LandiWetter MCP Server

a simple PoC on how to integrate a custom data-provider in an MCP Server

Local serverstdioGo

What is the LandiWetter MCP server?

LandiWetter MCP server exists for a simple reason — assistants are far more useful when they can act on LandiWetter directly instead of describing what you should do. a simple PoC on how to integrate a custom data-provider in an MCP Server.

What you get

This is a Model Context Protocol (MCP) server that provides Swiss weather forecast data from LandiWetter. The server allows you to search for Swiss locations and get detailed weather forecasts.

  • Search for Swiss locations by name
  • Get detailed weather forecasts for a specific location and date
  • Access both hourly and daily forecast data
  • Use as a tool or resource in MCP-compatible clients

What the assistant can call

Once LandiWetter is connected, these are the calls the assistant has available:

  • searchLocation — Parameters: - locationName: The name of the location to search for
  • getWeatherForecast — Parameters: - locationId: The location ID (e.g., G2661552) - date (optional): The date for the forecast (yyyy-MM-dd). Defaults to today

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. LandiWetter's toolset — searchLocation, getWeatherForecast — is a fair guide to whether it matches your workflow. It is maintained by nabossha; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the landiwetter mcp server does with a few real requests.

Available tools

ToolWhat it does
searchLocationParameters: - locationName: The name of the location to search for
getWeatherForecastParameters: - locationId: The location ID (e.g., G2661552) - date (optional): The date for the forecast (yyyy-MM-dd). Defaults to today

Example prompts to try

  • Use LandiWetter to searchLocation.
  • Use LandiWetter to getWeatherForecast.

Frequently asked questions

It connects LandiWetter to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (searchLocation, getWeatherForecast) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with LandiWetter directly.