Skip to main content
Glama
Hakuin123

OpenWeather-OneCall3-MCP

by Hakuin123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to OpenWeather-OneCall3-MCP

No user-submitted related servers found.

    Related Servers

    • mcp-weather

      githubmilind
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI assistants and LLMs to access real-time weather data and forecasts by connecting to the OpenWeatherMap API.
      -

    • OpenWeatherMap MCP Server

      robertn702
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides comprehensive weather data and forecasts through the OpenWeatherMap API, enabling AI assistants to access real-time weather information, forecasts, air quality data, and location services.
      11
      20 npm
      5
      MIT

    • weather-prediction-mcp-server

      joansolano
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides real-time weather data, forecasts, city weather comparisons, and travel recommendations using the OpenMeteo API, enabling AI agents to answer weather-related queries and suggest optimal travel conditions.
      -

    • mcp-open-meteo

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server provides access to Open-Meteo weather APIs including forecast, historical reanalysis, geocoding, air quality, marine weather, and flood risk data, enabling AI agents to retrieve weather information using natural language.
      22 npm
      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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct part of the weather API: current/forecast, historical time machine, and geocoding. There is no overlapping purpose, so an agent can easily select the right tool.

    Naming Consistency5/5

    All three tools use a consistent get_ prefix with snake_case noun phrases. The pattern is predictable and readable across the set.

    Tool Count5/5

    Three tools are well-scoped for a weather API wrapper, covering geocoding, current conditions with forecast, and historical data. Each tool earns its place without redundancy.

    Completeness4/5

    Core read operations are covered: geocoding, current/forecast, and historical weather. Minor gaps exist such as reverse geocoding, direct query by city name without a separate geocode step, or weather alerts/minutely data, but agents can work around these.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources