dailymeteo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DAILYMETEO_EMAIL | No | Your DailyMeteo account email. Together with DAILYMETEO_PASSWORD it enables daily values, credits, point history and area downloads. Sign up at https://app.dailymeteo.com/. | |
| DAILYMETEO_API_KEY | No | Alternative to email/password for daily values only (Account → API Keys). | |
| DAILYMETEO_PASSWORD | No | Your DailyMeteo account password. Together with DAILYMETEO_EMAIL it enables daily values, credits, point history and area downloads. | |
| DAILYMETEO_OUTPUT_DIR | No | Where CSV files and downloads are saved. | ~/dailymeteo |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
DailyMeteo: gridded weather data at 1 km for land areas worldwide, from 1961 to the present (the latest days lag by a few days), interpolated from GHCN-Daily, ECA&D and GSOD station observations. Variables: tmean, tmax, tmin (°C) and prcp (mm). Monthly/annual precipitation are totals, temperatures means.
Tools:
find_location: place name -> lat/lon. find_area: place name -> polygon for area downloads.
get_weather: values for a location, one or more variables, daily / monthly / annual. Monthly and annual are free. Daily costs 1 credit per day and variable (repeating the same request is not charged again); requests over 1000 credits need confirm_credits=true after the user agreed to the cost. Long series are summarised (with yearly aggregates) and saved as CSV.
get_climate_normals: normals 1961-1990 and 1991-2020 and their change (free).
account_status: plan and remaining credits.
request_point_history: every variable, daily, for one location, emailed as CSV (1 bulk credit).
estimate_area_download / request_area_download: daily rasters clipped to a polygon up to 3,000 km², emailed to the user. Always estimate and tell the user the cost before requesting.
app_link: link that opens the location and series in the DailyMeteo app (map and chart).
list_gridded_files / download_gridded_files: MeteoEurope1km raster archives (Europe, 1961-2020, incl. sea-level pressure) on Zenodo, free.
Values for the sea or outside the data are null. The data are interpolated grids, not station measurements. Cite results as: Sekulić, A., & Kilibarda, M. (2026). MeteoEurope1km (1961–2020): daily gridded meteorological dataset for Europe at a 1-km spatial resolution. Zenodo. https://doi.org/10.5281/zenodo.23264155
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 |
|---|---|
| find_locationA | Latitude and longitude of a place (OpenStreetMap Nominatim). If several match, ask the user which one. |
| find_areaA | Boundary polygon (WKT) and size of a named area, for estimate_area_download / request_area_download. |
| get_weatherA | Daily, monthly or annual values for one location and one or more variables, 1961 to the present. Monthly and annual values are free. Daily values cost 1 credit per day and variable and need the user's DailyMeteo API key or account (see the server instructions). Results include a summary per variable; series longer than 400 rows are not listed but summarised by year and saved as CSV. |
| get_climate_normalsA | Climate normals for 1961-1990 and 1991-2020 and the change (newer minus older). Free. Without |
| account_statusB | Plan and remaining credits: API credits (daily point and area data) and bulk credits (point history). |
| request_point_historyA | Every variable, daily, for one location — by default the whole record since 1961 — as CSV by email. Costs one bulk credit (bulk credits are separate from API credits). Preparing the file takes minutes. |
| estimate_area_downloadB | Credit cost of daily rasters clipped to an area (max 3,000 km²), and the account balance. |
| request_area_downloadA | Daily GeoTIFF rasters clipped to an area (max 3,000 km²), prepared on the server and emailed. Spends API credits: run estimate_area_download first and get the user's agreement to the cost. |
| app_linkB | Link that opens the location, variable and period on the DailyMeteo map with its chart and CSV export. |
| list_gridded_filesC | MeteoEurope1km archives on Zenodo (Europe, 1 km, 1961-2020, Cloud-Optimized GeoTIFF), free. Rasters are Equi7 Europe (EPSG:27704), Int16 in tenths of the unit (°C, mm, hPa), NoData -9999. |
| download_gridded_filesA | Download MeteoEurope1km archives (1-3.5 GB per year of daily data), verify MD5, optionally unzip. Interrupted downloads resume. Tell the user the total size (list_gridded_files) before large downloads. |
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 11 tools
Most tools target a clearly distinct action/resource: find_location, find_area, list/download gridded files, account_status, estimate/request area downloads, and climate normals are well separated. The main overlap is between get_weather and request_point_history, since both can return daily point data, though their delivery format, scope, and credit model are described well enough to distinguish them.
The set mostly follows a readable verb_noun pattern: find_location, find_area, get_weather, estimate_area_download, request_area_download, list_gridded_files, download_gridded_files, get_climate_normals, and request_point_history. Two tools, app_link and account_status, are noun phrases rather than verb-led, which is a minor deviation but not confusing.
With 11 tools, the surface is well scoped for a weather-data service covering point data, area data, gridded archives, climate normals, account credits, geocoding, and a convenience app link. Each tool appears to serve a real workflow rather than duplicating the same operation.
The set covers the core lifecycle: locate a point or area, estimate cost, request or retrieve data, list/download gridded archives, check credits, and get climate normals. Minor gaps remain, such as no explicit variable-discovery tool and no obvious way to check the status of emailed area/point-history requests, but agents can likely work around these with server instructions or the provided descriptions.