Skip to main content
Glama
evarness-ai

iris-weather-mcp

by evarness-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to iris-weather-mcp

No user-submitted related servers found.

    Related Servers

    • weather-mcp

      ninemindai
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes weather data from the free Open-Meteo API via decorator-driven MCP tools with Zod schemas, supporting stdio and HTTP transports.
      10 npm
      MIT

    • weather_mcp

      X-JS
      A
      license
      A
      quality
      B
      maintenance
      Provides real-time weather data by exposing a get_current_weather tool via MCP, using the Open-Meteo API over stdio JSON-RPC.
      1
      MIT

    • Weather MCP Server

      ajayamal
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides weather forecasts and active alerts for US locations using the National Weather Service API. It supports both local stdio and remote HTTP/SSE transport modes for flexible integration with MCP clients.
      87 npm
      GPL 3.0

    • Weather MCP Server

      newcoast27-hub
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server providing worldwide weather via the free Open-Meteo APIs (no API key needed). Runs fully self-contained in Docker as a streamable-HTTP MCP service.
      -

    • Mock MCP Apps Server

      dganesh5
      F
      license
      Not graded
      quality
      C
      maintenance
      A local, no-auth MCP server that exposes mocked weather forecast and supported cities tools over Streamable HTTP, enabling developers to test MCP integration with hosts like ChatGPT, Claude, and MCP Inspector.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one decodes a WMO weather code, while the other retrieves a daily forecast. There is no overlap or ambiguity in what each tool does.

    Naming Consistency4/5

    Both names use consistent snake_case with a shared `weather_` prefix, which makes them predictable. The pattern is noun-based rather than verb_noun (e.g., `weather_code_meaning` is a bit noun-heavy), so it is slightly less action-oriented than ideal, but still consistent.

    Tool Count3/5

    Two tools is on the thin side for a weather server; it covers forecast and code interpretation but lacks surface area for common weather queries. The count is borderline rather than clearly appropriate or excessive.

    Completeness3/5

    The surface covers daily forecasting and WMO code explanation, but missing current conditions, hourly data, historical weather, or alerts means common weather requests cannot be fulfilled. These are notable gaps for an agent expecting a general-purpose weather service.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources