Skip to main content
Glama
Sign In
narendrareddi

MCP Weather Agent

by narendrareddi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to MCP Weather Agent

No user-submitted related servers found.

    Related Servers

    • weather-mcp-server

      ariz-ahmad
      A
      license
      Not graded
      quality
      C
      maintenance
      A no-API-key-required MCP server that wraps Open-Meteo APIs to provide geocoding and weather forecast data, enabling city lookups and multi-day forecasts through tools, resources, and prompts.
      MIT

    • mcp-poc

      BhavanG
      F
      license
      Not graded
      quality
      D
      maintenance
      A proof-of-concept MCP server that provides weather information using the Open-Meteo API, with tools for greeting, getting weather by coordinates, and by location name.
      -

    • mcp-weather

      tarunmalpani
      A
      license
      A
      quality
      D
      maintenance
      A simple MCP server that exposes a get_weather tool to fetch real-time weather for any GPS coordinates using the Open-Meteo API, no API key required.
      1
      7 npm
      ISC

    • 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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: geocoding a place name, retrieving current conditions, and retrieving a forecast. There is no meaningful overlap between geocode_location and the weather retrieval tools, and current vs. forecast are well differentiated by their descriptions.

    Naming Consistency5/5

    All tool names use lowercase snake_case with a verb_noun style: geocode_location, get_current_weather, get_forecast. The two retrieval tools follow a uniform get_* pattern, and geocode_location fits the same verb-first convention.

    Tool Count5/5

    Three tools is an appropriate, well-scoped size for a weather agent. Each tool covers a necessary step in the core workflow: resolve location, get current conditions, get forecast, with no redundancy.

    Completeness4/5

    The core weather lookup workflow is complete: geocode a place, then retrieve current or forecast weather. Minor gaps such as lack of alerts, historical data, or reverse geocoding are not essential for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources