Saige Weather MCP Server
Related Servers
Alternatives to Saige Weather MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to fetch current weather conditions and forecasts for any city using the Open-Meteo API. Provides temperature, precipitation, and hourly forecast data through natural language queries.ISC
- AlicenseNot gradedqualityDmaintenanceEnables AI agents like GitHub Copilot to retrieve real-time weather data for any city using the Open-Meteo API, no API key required.9ISC
- AlicenseAqualityCmaintenanceProvides Open-Meteo weather tools that return both structured forecast data for the model and a weather card (image link or text) for the user, plus geocoding of place names to coordinates. Requires no API key and works over stdio or streamable HTTP.2Mozilla Public 2.0
- AlicenseNot gradedqualityBmaintenanceEnables 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 gradedqualityCmaintenanceEnables AI agents to retrieve real-time weather conditions and 7-10 day forecasts for any location via Open-Meteo, with no API key required.144 npmMIT
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusing it with another operation. Its purpose—fetching current weather for a location—is unambiguous.
The single name get_weather follows a clean verb_noun snake_case convention. A pattern cannot really be established with one tool, so it falls just short of a perfect score.
A weather server with exactly one tool is thin; users would reasonably expect forecast, multi-day, or historical queries. The single operation leaves the server under-scoped for its domain.
Only current conditions are exposed; there is no forecast, historical data, alerts, or unit/format options. These are significant gaps for a weather service and will force agents to fail on common forecast requests.