Yandex Weather MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host to bind the HTTP server (when using http transport) | 0.0.0.0 |
| PORT | No | Port to bind the HTTP server (when using http transport) | 3000 |
| LOG_LEVEL | No | Logging level (e.g., info, debug) | info |
| MCP_TRANSPORT | No | MCP transport mode: http or stdio | http |
| WEATHER_DB_PATH | No | Path to the SQLite database file for scheduler persistence | ./data/weather.db |
| CACHE_TTL_SECONDS | No | Cache time-to-live in seconds | 600 |
| YANDEX_WEATHER_LANG | No | Language for weather data (e.g., ru_RU, en_US) | ru_RU |
| YANDEX_WEATHER_API_KEY | Yes | API key for Yandex Weather API | |
| YANDEX_WEATHER_API_URL | No | Override the default Yandex Weather API endpoint | https://api.weather.yandex.ru/v2/forecast |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_weatherB | Get current weather by coordinates |
| get_weather_forecastC | Get weather forecast by coordinates |
| get_weather_summaryC | Build a short human-readable weather summary |
| compare_weatherC | Compare current weather in two locations |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: current weather, forecast, comparison between two locations, and a human-readable summary. No overlapping functionality.
Three tools follow the 'get_weather_*' pattern, while 'compare_weather' uses a different verb but still follows verb_noun convention. The naming is mostly consistent.
Four tools is an appropriate count for a weather server, covering core needs without being excessive or sparse.
Covers essential weather operations (current, forecast, comparison, summary). Missing historical data or alerts, but these are minor gaps that agents can work around.