Skip to main content
Glama

Related Servers

Alternatives to openmeteo-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides comprehensive access to Open-Meteo weather APIs, including forecasts, historical data, air quality, marine weather, and geocoding, enabling LLMs to retrieve weather information and location data.
      17
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Provides comprehensive weather data (forecasts, historical, air quality, marine) from Open-Meteo through 12 tools, with support for single and batch location queries.
      12
      1
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Provides comprehensive access to Open-Meteo APIs for weather forecasts, historical data, air quality, and marine conditions. It enables LLMs to query specialized meteorological models, perform geocoding, and access advanced climate or flood projections.
      17
      1,237 npm
      73
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides weather forecasts and geocoding lookup using free Open-Meteo APIs, enabling LLMs to query real-time weather and multi-day forecasts for any location.
      1
      ISC
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time weather data via 12 tools (current weather, forecasts, air quality, umbrella advice, etc.) using Open-Meteo and FastMCP, enabling LLMs to answer weather-related queries.
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides weather forecast tools using Open-Meteo, enabling users to get current conditions, multi-day forecasts, and umbrella recommendations through natural language queries.
      -

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct weather data type or workflow step: geocoding, current conditions, daily forecast, hourly forecast, air quality, and historical weather. There is no meaningful overlap, and the descriptions clearly indicate when to use each tool.

    Naming Consistency4/5

    All tools use snake_case and most follow a clear get_<resource> pattern. geocode_location is a minor deviation from the get_ prefix, but it remains readable and predictable in context.

    Tool Count5/5

    Six tools are well-scoped for a weather API server, covering the main forecast and historical data needs without redundancy. Each tool has a clear purpose and earns its place.

    Completeness5/5

    The surface covers geocoding plus current, daily, hourly, historical, and air-quality data, which are the core operations for an Open-Meteo-style server. No obvious lifecycle gaps or dead ends are apparent for this domain.