openmeteo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Weather and climate tools backed by the free, keyless Open-Meteo API. Start with geocode_location if you only have a place name; its latitude/longitude feed every other tool. All tools are read-only and safe to retry — identical calls within the cache TTL return cached data.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocode_locationA | Resolve a place name to coordinates, country, timezone and population. Call this first when you only have a place name, then pass the returned latitude/longitude into any weather tool. |
| get_current_weatherA | Current weather at a coordinate: temperature, apparent temperature, humidity, precipitation, wind, and a plain-language sky description. |
| get_daily_forecastA | Day-by-day forecast (up to 10 days): highs/lows, precipitation amount and probability, max wind, UV index, and sunrise/sunset, in local time. |
| get_hourly_forecastA | Hour-by-hour forecast (up to 72 hours): temperature, apparent temperature, precipitation probability and amount, wind, and sky description. |
| get_air_qualityB | Hourly air quality (up to 48 hours): US EPA AQI plus PM2.5, PM10, ozone and NO2 concentrations. |
| get_historical_weatherA | Historical daily weather from the Open-Meteo archive (about 1950 to roughly five days ago): highs/lows, precipitation, snowfall and sky conditions. Ranges are capped at 366 days per call. |
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 6 tools
Each tool targets a distinct weather data type or workflow step: geocoding, current conditions, daily forecast, hourly forecast, air quality, and historical weather. There is no meaningful overlap, and the descriptions clearly indicate when to use each tool.
All tools use snake_case and most follow a clear get_<resource> pattern. geocode_location is a minor deviation from the get_ prefix, but it remains readable and predictable in context.
Six tools are well-scoped for a weather API server, covering the main forecast and historical data needs without redundancy. Each tool has a clear purpose and earns its place.
The surface covers geocoding plus current, daily, hourly, historical, and air-quality data, which are the core operations for an Open-Meteo-style server. No obvious lifecycle gaps or dead ends are apparent for this domain.