Это сервер Model Context Protocol (MCP), который предоставляет данные прогноза погоды в Швейцарии от LandiWetter. Сервер позволяет вам искать местоположения в Швейцарии и получать подробные прогнозы погоды.
Поиск швейцарских населенных пунктов по названию
Получите подробные прогнозы погоды для определенного места и даты
Доступ к данным как почасовых, так и ежедневных прогнозов
Использование в качестве инструмента или ресурса в MCP-совместимых клиентах
Related MCP server: meteo-swiss-mcp
Клонировать репозиторий
Установите зависимости:
npm installЗапустите сервер с помощью:
npm startЭто запустит сервер MCP с использованием транспорта stdio, что сделает его совместимым с клиентами MCP, такими как Claude Desktop.
Открыть рабочий стол Клода
Перейдите в Настройки > MCP > Добавить пользовательский сервер.
Настройте, указав следующие данные:
Имя: ЛандиВеттер
Команда: node /path/to/landiwetter-mcp/src/index.js
Сохраните и включите сервер
После интеграции сервера с Claude Desktop вы сможете использовать подсказки на естественном языке для доступа к прогнозам погоды:
Чтобы получить прогноз погоды:
What's the weather forecast for Bern, Switzerland?Чтобы получить прогноз погоды на конкретную дату:
What's the weather forecast for Zürich on 2025-05-10?Поиск швейцарских населенных пунктов по названию.
Параметры:
locationName : Название местоположения для поиска
Пример:
Please search for locations named "Zürich"Получите подробный прогноз погоды для определенного места.
Параметры:
locationId : идентификатор местоположения (например, G2661552)
date (необязательно): дата прогноза (гггг-ММ-дд). По умолчанию сегодня
Пример:
Please get the weather forecast for location ID G2661552Доступ к прогнозам погоды через URI ресурса.
Шаблон URI: weather://{location}/{date}
Где:
location : название местоположения (например, «Цюрих»)
date (необязательно): дата прогноза (гггг-ММ-дд). По умолчанию сегодня
Пример:
Please check the resource at weather://Zürich/2025-05-03| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Optional: The date for the forecast (yyyy-MM-dd). Defaults to today | |
| locationId | Yes | The location ID (e.g., G2661552) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| locationName | Yes | The name of the location to search for |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0getWeatherForecastsearchLocationScored 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.
Swiss weather data for AI assistants — forecasts, measurements, stations, pollen.
Swiss weather and federal geodata from MeteoSwiss and swisstopo on data.geo.admin.ch — find…
Current weather and 7-day forecast for any place (MET Norway). $0.006/call via x402.
Weather forecasts from MET Norway (Yr): geocoding plus hourly forecasts worldwide.