nws-mcp
Related Servers
Alternatives to nws-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.213 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides weather forecasts and alerts for US locations via the National Weather Service API, enabling AI assistants to deliver real-time weather information.28 npmISC
- FlicenseNot gradedqualityDmaintenanceProvides 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.-
- AlicenseAqualityBmaintenanceProvides US weather forecasts, current conditions, alerts, earthquakes, elevation, and geocoding via keyless US-government data feeds. Enables AI agents to access real-time weather and geospatial data without API keys.6MIT
- AlicenseAqualityBmaintenanceEnables Claude to fetch live US National Weather Service data: active alerts for a state or territory, and up-to-7-day forecasts for any latitude/longitude in the US. Needs no API key, so users can simply ask in plain language about warnings, watches, and upcoming conditions.211 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides real-time weather alerts and forecasts from the National Weather Service for US locations, integrating with AI assistants via the Model Control Protocol.-
TDQS
Scored across 5 tools
Each tool targets a distinct data product: multi-day forecast, hourly forecast, active alerts, latest observation, and grid metadata. The only near-neighbor pair (get_forecast vs get_hourly_forecast) is unambiguously separated by name and by the explicit 'multi-day periods' vs 'hour-by-hour' descriptions.
All five tools follow a strict snake_case get_<resource> pattern with no verb or casing deviations. The naming reads predictably and maps cleanly onto the returned resource.
Five tools is well within the well-scoped range, and each tool maps to a genuinely different NWS endpoint with no redundant overlap. Nothing feels padded or missing at the count level.
The core weather surface (daily forecast, hourly forecast, current conditions, alerts, grid metadata) is fully covered with no dead ends for typical use. Minor gaps exist around historical observations, station search, and narrative forecast-discussion text products, which agents would have to work around.