Weather MCP Server
Related Servers
Alternatives to Weather MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that provides real-time US weather alerts and forecasts via the NOAA National Weather Service API.-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides tools to fetch weather alerts for US states and forecasts based on latitude/longitude coordinates using the US National Weather Service API.255 npm1MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that provides US weather forecasts and active alerts using the National Weather Service API.2-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides real-time weather alerts and forecasts using the National Weather Service API.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models to fetch weather alerts and detailed forecasts for US locations using the National Weather Service API.55 npmGPL 3.0
- FlicenseNot gradedqualityDmaintenanceProvides weather forecasts, current conditions, and alerts for US locations using the National Weather Service API.1-
TDQS
Scored across 3 tools
The tools have no coherent domain overlap, making them highly ambiguous as a set. 'get-alerts' and 'get-forecast' relate to weather, while 'get-feishu-doc' is unrelated (document retrieval), causing clear confusion about the server's purpose and tool selection.
Naming is inconsistent with mixed conventions: 'get-alerts' and 'get-forecast' use kebab-case with a 'get-' prefix, while 'get-feishu-doc' uses kebab-case but includes a non-English term, breaking pattern. The verbs are consistent ('get'), but the overall style lacks uniformity.
With only 3 tools, the count is too low for a coherent weather server, as it lacks essential operations like historical data or radar. The inclusion of an unrelated document tool further dilutes the scope, making the set feel incomplete and mismatched.
The tool set is severely incomplete for a weather domain, missing basic CRUD operations like update or delete, and lacking coverage for key weather aspects (e.g., current conditions, historical data). The unrelated document tool creates a gap in domain coherence, making the surface unusable for weather-related tasks.