Skip to main content
Glama
wttr.in Weather MCP

wttr.in Weather MCP

by zhbjerry

Related Servers

Alternatives to wttr.in Weather MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides 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
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides 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.
      6
      ISC

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues