Skip to main content
Glama
ominiverdi

open-meteo-mcp-lite

by ominiverdi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to open-meteo-mcp-lite

No user-submitted related servers found.

    Related Servers

    • weather-mcp-server

      raviraval79
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that wraps the Open-Meteo API to provide current weather, forecasts, and historical data for any location without requiring an API key.
      MIT

    • mcp-weather

      DaniBencz
      F
      license
      Not graded
      quality
      B
      maintenance
      A minimal MCP server that provides current weather and forecasts for any city using the free Open-Meteo API, no API key required.
      9 npm
      -

    • MCP Weather Free

      microagents
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides real-time weather data, hourly forecasts, and daily summaries using the free Open-Meteo API with no API key required. It enables users to search for weather conditions by specific coordinates or city names across multiple measurement units.
      2
      MIT

    • Simple Weather MCP

      markmehere
      A
      license
      Not graded
      quality
      D
      maintenance
      A cross-platform MCP server that provides weather forecasts by coordinates, location name, or IP address without requiring API keys. It leverages Open Meteo and OpenStreetMap to deliver fast, single-query weather lookups.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: two manage default location, one searches locations, and three retrieve weather data (current, daily forecast, hourly forecast). Potential overlap between get_forecast and get_hourly_forecast is resolved by descriptions explicitly distinguishing daily vs hourly granularity.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: get_* for retrieval, set_* for configuration, search_* for lookup. The naming is predictable and uniform across the entire set.

    Tool Count5/5

    Six tools is well-scoped for a weather API lite server, covering configuration, location search, and three data retrieval modes. The count is neither sparse nor excessive, and each tool serves a necessary function.

    Completeness5/5

    The tool set covers the core workflow: search location, set/get default location, get current weather, and get daily or hourly forecasts. Minor omissions like clearing a default location or historical data are acceptable given the 'lite' designation, and no critical operation is missing.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources