LandiWetter MCP Server
# LandiWetter MCP Server
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.
<a href="https://glama.ai/mcp/servers/@nabossha/mcp-landiwetter">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@nabossha/mcp-landiwetter/badge" alt="LandiWetter Server MCP server" />
</a>
## Features
- 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
## Installation
1. Clone the repository
2. Install dependencies:
```
npm install
```
## Usage
### Starting the Server
Run the server with:
```
npm start
```
This starts the MCP server using the stdio transport, making it compatible with MCP clients like Claude Desktop.
### Integrating with Claude Desktop
1. Open Claude Desktop
2. Go to Settings > MCP > Add custom server
3. Configure with the following details:
- Name: LandiWetter
- Command: `node /path/to/landiwetter-mcp/src/index.js`
4. Save and enable the server
### Example Claude Prompts
Once the server is integrated with Claude Desktop, you can use natural language prompts to access weather forecasts:
**To get a weather forecast:**
```
What's the weather forecast for Bern, Switzerland?
```
**To get a weather forecast for a specific date:**
```
What's the weather forecast for Zürich on 2025-05-10?
```
## Available Tools
### searchLocation
Search for Swiss locations by name.
Parameters:
- `locationName`: The name of the location to search for
Example:
```
Please search for locations named "Zürich"
```
### getWeatherForecast
Get a detailed weather forecast for a specific location.
Parameters:
- `locationId`: The location ID (e.g., G2661552)
- `date` (optional): The date for the forecast (yyyy-MM-dd). Defaults to today
Example:
```
Please get the weather forecast for location ID G2661552
```
## Available Resources
### weather-forecast
Access weather forecasts through a resource URI.
URI Template: `weather://{location}/{date}`
Where:
- `location`: The name of the location (e.g., "Zürich")
- `date` (optional): The date for the forecast (yyyy-MM-dd). Defaults to today
Example:
```
Please check the resource at weather://Zürich/2025-05-03
```TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: getWeatherForecast retrieves weather data, while searchLocation finds geographic locations. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool based on the task.
Both tools use a verb_noun pattern (getWeatherForecast and searchLocation), which is consistent and predictable. The minor deviation is the use of camelCase instead of snake_case, but this does not hinder readability or coherence within the set.
With only 2 tools, the server feels thin for a weather and location domain. While it covers basic retrieval and search, it lacks essential operations like updating preferences, handling alerts, or managing saved locations, making the scope appear incomplete and underdeveloped.
Inferring the domain as weather and location services, the tool set is severely incomplete. It only provides forecast retrieval and location search, missing critical operations such as current weather data, historical forecasts, location management, or user-specific configurations, which are typical for such services.