Open Meteo MCP Server
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.
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_weatherC | Get current weather conditions for a specific location |
| get_weather_forecastC | Get weather forecast (hourly and daily) for a location |
| get_historical_weatherB | Get historical weather data for a specific location and date range |
| search_locationsB | Search for locations by name and get their coordinates |
| get_air_qualityC | Get air quality data and forecasts for a location |
| get_marine_weatherC | Get marine weather forecasts including waves and ocean conditions |
| get_climate_dataC | Get climate change scenarios and long-term climate data |
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 7 tools
Each tool has a clearly distinct purpose targeting different meteorological data types (air quality, climate, current weather, historical weather, marine weather, forecasts, and location search). There is no overlap or ambiguity in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_air_quality, get_current_weather). The naming is uniform across all seven tools, with no deviations in style or convention.
With 7 tools, the server is well-scoped for a weather and climate data service. Each tool serves a specific, non-redundant function, and the count is appropriate for covering key meteorological queries without being overwhelming or insufficient.
The toolset provides comprehensive coverage for the meteorological domain, including current conditions, forecasts, historical data, air quality, climate scenarios, marine weather, and location search. There are no obvious gaps, and the tools support a full range of weather-related workflows.