open-meteo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPEN_METEO_FORECAST_URL | No | Forecast endpoint (full endpoint URL). Optional. | https://api.open-meteo.com/v1/forecast |
| OPEN_METEO_GEOCODING_URL | No | Geocoding endpoint (full endpoint URL). Optional. | https://geocoding-api.open-meteo.com/v1/search |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Weather data from Open-Meteo (free, no API key). First call search_locations to turn a place name into coordinates; if several places share the name (e.g. Córdoba in AR, ES, MX), pick by context or ask the user, or retry with country_code. Then call get_current_weather or get_forecast with those coordinates (if the user already gave coordinates you can skip the search). Times are local to the place's timezone, which every result states. Weather codes follow WMO (see weather://wmo-codes). Weather data by Open-Meteo.com, licensed CC BY 4.0: attribute it when you show it. The free API is for non-commercial use only and is limited to 600 calls/min, 5,000/hour and 10,000/day.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_locationsA | Search places by name worldwide. Returns name, region, country, coordinates, timezone and id; use the coordinates with get_current_weather or get_forecast. An ambiguous name returns several results. |
| get_current_weatherA | Current conditions (temperature, feels-like, humidity, precipitation, weather code, wind, day/night) at the given coordinates, with the local time of the place. Use search_locations first if you only have a place name. |
| get_forecastA | Daily forecast for up to 16 days (weather, min/max temperature, precipitation and its max probability, max wind) at the given coordinates and, with hourly: true, an hourly forecast for up to 48 hours (temperature, precipitation probability, weather). Times are local to the place. Use search_locations first if you only have a place name. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| wmo-codes | Meaning of the weather_code values returned by the tools |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: location search, current conditions, and forecast. The descriptions explicitly guide sequencing, reducing ambiguity between current weather and forecast.
All tool names follow a consistent verb_noun pattern: search_locations, get_current_weather, get_forecast. The convention is predictable and readable.
Three tools are well-scoped for a focused weather server: geocoding, current conditions, and forecast. Each tool earns its place without feeling bloated or overly thin.
The core workflow is covered: find a place, get current weather, and get a forecast. Minor gaps exist for historical weather or alerts, but the stated purpose is well served.