weather-intel-mcp
Related Servers
Alternatives to weather-intel-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to access real-time US weather forecasts and alerts through the National Weather Service API.26 npmMIT
- FlicenseBqualityDmaintenanceProvides real-time US weather alerts and forecasts by integrating with the National Weather Service API. It enables AI assistants to fetch state-specific alerts and detailed local forecasts using geographic coordinates.21-
- FlicenseNot gradedqualityCmaintenanceProvides real-time weather data, forecasts, alerts, and travel recommendations for US locations using the National Weather Service API, enabling agents to answer weather-related queries.-
- AlicenseNot gradedqualityDmaintenanceProvides weather forecasts and alerts for US locations via the National Weather Service API, enabling AI assistants to deliver real-time weather information.13 npmISC
- FlicenseBqualityCmaintenanceEnables dynamic, real-time weather alerts and forecasts from the National Weather Service through AI agentic tool calls.22-
- FlicenseNot gradedqualityCmaintenanceProvides weather tools using the National Weather Service API, enabling AI agents to retrieve current weather, multi-day forecasts, and simple weather-based recommendations for U.S. locations.-
TDQS
Scored across 6 tools
Each tool targets a clearly distinct resource and action: geocoding vs. forecast vs. current conditions vs. alerts vs. earthquakes vs. elevation. weather_forecast and weather_current are explicitly differentiated (multi-day vs. latest observations), and the descriptions repeatedly clarify the geocode-first workflow. No plausible misselection.
Names are readable and mostly follow a snake_case noun pattern, but the set mixes a bare verb (geocode) with weather_-prefixed tools, and even within that prefix the suffix style varies (weather_forecast/current vs. weather_alerts). Minor inconsistency, still predictable enough.
Six tools is well-scoped for a weather-intelligence server, covering the core workflow without redundancy. Each tool earns its place with a distinct data source and purpose.
The surface covers a full practical lifecycle: geocode to coordinates, then forecast, current, alerts, elevation, plus earthquakes. Gaps are minor (no historical/archive data, no hourly granularity, marine forecast only partial), and agents can work around them.