wttr.in Weather MCP
Related Servers
Alternatives to wttr.in Weather MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables access to authoritative US National Weather Service forecasts, hourly forecasts, active alerts, and station observations with no authentication required.81 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides current weather data and hourly forecasts for any location worldwide using the Open-Meteo API, accessible through HTTP transport without requiring an API key.13 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides live weather data and forecasts for any location worldwide through both REST API and MCP endpoints. Supports current weather, multi-day forecasts, and various location formats including city names, coordinates, ZIP codes, and airport codes.1-
- AlicenseAqualityDmaintenanceProvides hourly and daily weather forecasts using the free Open-Meteo API without requiring an API key.219 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides weather data including current conditions, daily forecasts up to 16 days, and hourly forecasts up to 7 days, using the free Open-Meteo API with no API key required.1MIT
- AlicenseAqualityCmaintenanceProvides real-time, historical, and forecasted weather data for any location worldwide using the Open-Meteo API. It includes specialized tools for agricultural growing conditions, weather alerts, and up to 16 days of forecasts across multiple transport modes.6ISC
TDQS
Scored across 2 tools
get_weather is a convenience tool for current conditions/forecast, while wttr_request exposes wttr.in's raw output formats and query options, so the intent separation is clear. There is some overlap since wttr_request with JSON format could reproduce get_weather's output, but the descriptions steer selection reasonably well.
get_weather follows a verb_noun convention, but wttr_request mixes a service-prefix with a noun and no action verb. The two names are readable and interpretable but do not follow a single predictable pattern.
Two tools is thin for a weather server, and the entire surface leans on one catch-all raw-request tool. It's defensible for a simple wttr.in wrapper, but borderline minimal given typical expectations for forecast, location lookup, and formats.
Current weather, up to three-day forecast, and arbitrary wttr.in formats/options via wttr_request are all covered, which is close to the full domain of the service. Minor gaps exist (no dedicated geocoding/location search, forecast length capped at three days), but agents can work around these with the raw request tool.