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.
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": 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 an account or API key in the server configuration. 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 have clearly distinct roles: geographic lookup (find_location vs find_area), archive listing/downloading, point data, normals, credit estimation, and linking. The main potential confusion is between get_weather and request_point_history, which both return point time-series data (differing only by credit type and delivery method), and between estimate_area_download and request_area_download, though the estimate/request pairing is standard and descriptions clarify it.
The set follows a mostly predictable verb_noun snake_case convention (list_gridded_files, download_gridded_files, get_weather, estimate_area_download, request_area_download). The only deviations are account_status and app_link, which are noun phrases without a leading verb, but they remain readable and unambiguous.
Eleven tools is well within the ideal range and each one covers a distinct capability: discovery, archival download, geocoding, point queries, normals, credits/account, bulk history, area estimation/download, and sharing. No tool appears redundant or trivially included.
The surface covers the full workflow from locating a place through estimating cost, querying data, and retrieving results, with an account/credit check and a share link. Minor gaps exist around async job tracking for the emailed point-history and area-download requests (no status or cancel tool) and no in-tool authentication/account creation, though these are workable via email delivery and server configuration.