Skip to main content
Glama
clarehancock

Open-Meteo MCP Server

by clarehancock
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Open-Meteo MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-weather-server

      srathish
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides 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

    • mcp-weather

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to retrieve real-time weather conditions and 7-10 day forecasts for any location via Open-Meteo, with no API key required.
      4 npm
      MIT

    • Weather MCP Server

      JeremyMorgan
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to retrieve current weather, forecasts, and summaries for any global location using the Open-Meteo API, with no API key required.
      5 npm
      Creative Commons Zero v1.0 Universal

    • Weather MCP Server

      minidantre-db
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to retrieve current weather conditions and forecasts for specified locations by geocoding places and pulling data from Open-Meteo, with optional natural-language summaries via Groq.
      1
      -

    • Weather MCP Server

      jefercort
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      -
    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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: geocoding converts place names to coordinates, while the other two retrieve weather data. The current weather and forecast tools are differentiated by time horizon and description.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: geocode_location, get_current_weather, get_weather_forecast. The naming style is uniform and predictable.

    Tool Count5/5

    With 3 tools, the server is tightly scoped for its purpose: location resolution, current conditions, and forecast. Each tool earns its place and the count feels complete without redundancy.

    Completeness4/5

    The core weather lookup flow is fully covered: geocode a place name, get current conditions, or get a forecast. Minor gaps exist such as historical weather data or alerts, but these are not essential for the apparent primary use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources