mcp-weather-server
Related Servers
Alternatives to mcp-weather-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to get weather forecasts for any city using the Open-Meteo API through natural language in Claude Desktop or VS Code.ISC
- FlicenseBqualityCmaintenanceEnables Claude to retrieve current conditions, 5-day forecasts, and air quality/pollutant data for locations worldwide using Open-Meteo, with no API key required.21-
- AlicenseNot gradedqualityCmaintenanceEnables Claude to fetch real-time weather data for any city using the OpenWeatherMap API.13 npmMIT
- FlicenseAqualityDmaintenanceProvides current weather and forecast data for any city via OpenWeatherMap. Can be used with Ollama or Claude Desktop for natural-language weather queries.2-
- AlicenseAqualityCmaintenanceEnables users to geocode city names and retrieve current weather conditions plus a 1–7 day forecast through a public weather API, with no API key required, for MCP clients such as Claude Desktop or Cursor.2MIT
- FlicenseNot gradedqualityDmaintenanceProvides real-time weather data to Claude using the Open-Meteo API, with no API key required. Enables natural language queries like 'What's the weather in Tokyo?'.-
TDQS
Scored across 3 tools
Each tool targets a distinct temporal or comparative view (current, forecast, multi-city comparison), and descriptions make the boundaries explicit. compare_cities partially overlaps with get_current applied to several cities, but the added ranking output justifies its separate existence.
All three tools follow the same snake_case verb_noun pattern (get_current, get_forecast, compare_cities). The verbs are accurate and predictable, so an agent can guess a tool's intent from its name.
Three tools is on the lean side, but each covers a genuinely distinct weather-query pattern and nothing feels redundant. It sits at the low edge of a well-scoped surface rather than being thin to the point of uselessness.
The core weather workflows (current conditions, daily outlook, multi-city comparison) are covered with no dead ends. Gaps exist around hourly breakdowns, historical data, alerts, and city/geocoding lookup, but agents can work around these for typical queries.