Skip to main content
Glama
le-yo

MCP Weather Server

by le-yo

Related Servers

Alternatives to MCP Weather Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      F
      maintenance
      A simple Model Context Protocol server that provides real-time weather data to AI agents like GitHub Copilot, allowing users to get current weather information for any city through natural language queries.
      2
      9 npm
      97
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A lightweight Model Context Protocol (MCP) server that gives AI assistants the ability to fetch real-time weather data for any city using the OpenWeatherMap API.
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that retrieves current weather information for any city using the OpenWeatherMap API, designed for integration with Claude Code.
      1
      10 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides weather information using the Open-Meteo API, allowing users to get current weather for specific cities and retrieve weather data for date ranges.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A TypeScript-based Model Context Protocol server that enables Claude Desktop to fetch real-time weather data via external weather APIs. It provides a simple integration for users to query current weather information through natural language interactions.
      7 npm
      -

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation3/5

    The tools have some overlap in purpose, particularly getWeather and getWeatherForecast, which could cause confusion about their distinct scopes (current vs. multi-day forecast). However, getHourlyWeather and lookupCity are clearly distinct, and descriptions help clarify the differences between the overlapping tools.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., getHourlyWeather, getWeather, getWeatherForecast, lookupCity), with all tools using camelCase. There is a minor deviation with lookupCity not starting with 'get', but the pattern is still readable and predictable overall.

    Tool Count5/5

    With 4 tools, the server is well-scoped for a weather domain, covering current, hourly, and forecast data, plus city lookup. Each tool earns its place without feeling excessive or insufficient for the apparent purpose.

    Completeness4/5

    The tool surface covers core weather operations (current, hourly, forecast) and city lookup, providing good coverage for typical agent workflows. A minor gap exists in not including historical weather data or alerts, but agents can work around this with the available tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues