dailymeteo-mcp
Related Servers
Alternatives to dailymeteo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceGlobal weather intelligence for AI assistants providing 10 weather tools — forecasts, historical data, air quality, marine, geocoding, elevation, and climate projections at 1km resolution with 80+ years of archive.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access NOAA's national climate archive—GHCN-Daily observations, station search, and dataset catalog—without an API key.2 npmMIT
- FlicenseNot gradedqualityDmaintenanceExposes public weather and climate data through a standardized API, allowing AI agents to retrieve current conditions, 7-day forecasts, and historical data. It enables weather-aware automation and data enrichment for conversational agents and travel planning.-
- AlicenseNot gradedqualityFmaintenanceProvides weather and climate intelligence for AI agents, including current conditions, forecasts, historical data, severe-weather alerts, agricultural outlook, and travel conditions via free and paid tools.1MIT
- FlicenseAqualityBmaintenanceEnables AI assistants to retrieve current weather conditions and forecasts for any location via natural language, with optional AI-generated summaries.1-
- AlicenseAqualityCmaintenanceGives AI assistants read-only, key-free access to Sentinel-2 NDVI time series, ESA WorldCover land-cover shares, and Copernicus 30 m elevation and slope for a point or small area, returning the scene IDs, units, and caveats behind every number. Built-in sanity checks and a verify tool recompute key values through an independent path so the assistant can flag cloudy, low-confidence, or mismatched results instead of guessing.6MIT
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.