Skip to main content
Glama
Cyreslab-AI

windy-webcams-mcp-server

by Cyreslab-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to windy-webcams-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • weather-mcp

      idrabenia
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing weather data via the Open-Meteo API, including geocoding, current conditions, daily and hourly forecasts, and city lookup. No API key required, with support for multiple units and transport types.
      1
      MIT

    • windscout-mcp

      jwillert
      A
      license
      A
      quality
      D
      maintenance
      MCP server for wind forecasts, live measurements, wave forecasts, and tides, enabling kite and surf spot checks via AI assistants.
      5
      6 npm
      MIT

    • mcp-server

      keijumasukawa
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides tools to retrieve weather information from a weather API, supporting both local stdio and remote Streamable HTTP transports.
      239 npm
      1
      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.5/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target distinct query types (by ID, by location, by category, nearby, map clusters, reference lists), but search_webcams with filters overlaps conceptually with the dedicated by_location/by_category/nearby tools, creating mild ambiguity. The reference-list tools (regions, continents, countries, categories) are clearly distinct.

    Naming Consistency4/5

    The dominant pattern is get_webcams_by_* and get_<reference-entity>, which is consistent and predictable. Two exceptions, search_webcams and export_all_webcams, break the pattern but are still clear and understandable.

    Tool Count5/5

    With 11 tools, the server is well-scoped for a read-only webcam data API. Each tool serves a clear purpose, and the count is within the ideal 3-15 range without feeling bloated.

    Completeness5/5

    The surface covers the full range of likely queries: reference data, search, detail lookup, filtered listing by location/category, proximity search, map-friendly clusters, and bulk export. For a read-only public webcam API, there are no obvious dead ends or missing operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources