weather-mcp
Related Servers
Alternatives to weather-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides weather forecasts and geocoding lookup using free Open-Meteo APIs, enabling LLMs to query real-time weather and multi-day forecasts for any location.18 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables agents to fetch global current conditions, air quality (PM2.5, PM10, O₃, NO₂, SO₂, CO, US/EU AQI), UV index, wind, sunrise/sunset and 1–16 day forecasts with optional hourly rows via Open-Meteo, no API key needed. Returns a localized human-readable summary plus complete JSON, resolving locations by city name, coordinates, or public IP over stdio MCP.MIT
- AlicenseNot gradedqualityDmaintenanceProvides live weather data (current conditions, forecasts) and city geocoding through Open-Meteo API, enabling AI assistants to answer weather queries without an API key.MIT
- AlicenseNot gradedqualityBmaintenanceGives language models weather tools for place search, multi-day forecasts, and location comparison, with no API key or configuration required.79 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides weather forecast tools using Open-Meteo, enabling users to get current conditions, multi-day forecasts, and umbrella recommendations through natural language queries.-
- AlicenseAqualityDmaintenanceProvides comprehensive access to Open-Meteo weather APIs, including forecasts, historical data, air quality, marine weather, and geocoding, enabling LLMs to retrieve weather information and location data.171,258 npm1MIT
TDQS
Scored across 2 tools
get_forecast and geocode have clearly distinct purposes: one fetches weather data, the other resolves place names to coordinates. The get_forecast description even explains when to use geocode first to disambiguate, so there is no realistic misselection risk.
get_forecast follows a verb_noun pattern, while geocode is a bare verb with no noun. Both are snake_case and readable, so the deviation is minor rather than confusing.
Two tools is thin for a weather server; a full forecast surface typically warrants separate helpers (current conditions, hourly, alerts, history). The set is coherent but minimal, and geocode exists mainly as a support tool for get_forecast.
The forecast tool covers current conditions plus a configurable multi-day daily forecast with units, language, and card rendering, which is the core weather workflow. Gaps remain for hourly forecasts, historical/archive data, and severe-weather alerts, but agents can work around these.