Weather API MCP Server
Related Servers
Alternatives to Weather API MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides weather query capabilities including current weather, daily/hourly forecasts, air quality data, and weather alerts through QWeather API integration with JWT-based authentication.-
- FlicenseAqualityDmaintenanceEnables querying real-time weather, forecasts, and warnings for Chinese cities via the QWeather API.3-
- AlicenseNot gradedqualityBmaintenanceProvides comprehensive weather data including forecasts, air quality, weather alerts, historical data, and astronomical information through the Hefeng Weather API. Supports real-time weather, multi-day forecasts, hourly predictions, and specialized data like sunrise/sunset times and precipitation forecasts.4MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying weather forecasts (1-7 days) and meteorological warnings for Chinese cities using the QWeather API. Supports detailed weather data including temperature, humidity, wind, precipitation, UV index, and real-time weather alerts.2-
- AlicenseBqualityDmaintenanceProvides weather forecast data for locations in China through HeFeng Weather API, supporting real-time, hourly, and daily forecasts with full Chinese weather descriptions.312 npmISC
- AlicenseAqualityAmaintenanceEnables querying real-time, hourly, weekly, and historical weather data, as well as weather alerts, using the Caiyun Weather API.515 PyPI47MIT
TDQS
Scored across 4 tools
The tools have overlapping purposes that could cause confusion. getWeather, getHourlyWeather, and getWeatherForecast all retrieve weather data for a location, differing only in time granularity. While descriptions clarify the distinctions, an agent might misselect between them without careful reading. The lookupCity tool is clearly distinct, but the three weather retrieval tools create ambiguity.
Naming is mostly consistent with a verb_noun pattern, though there are minor deviations. getWeather, getHourlyWeather, and getWeatherForecast follow a clear get_<type>Weather pattern, while lookupCity uses a different verb (lookup vs. get). All use camelCase consistently, making them readable despite the verb variation.
Four tools is well-scoped for a weather API server. Each tool earns its place: current weather, hourly forecast, multi-day forecast, and city lookup provide complete coverage without bloat. This count aligns with typical server scopes (3-15 tools) and avoids being too thin or heavy.
The tool set covers core weather API operations effectively, with minor gaps. It includes current conditions, short-term and long-term forecasts, and location lookup, enabling agents to handle most weather queries. However, there are no tools for historical weather data or alerts, which could be useful extensions for the domain.