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.76 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 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.