MCP Weather Sample
Related Servers
Alternatives to MCP Weather Sample
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server built with the mcp-framework to provide weather-related tools and data to AI clients. It enables integration of weather capabilities and custom tools into the MCP ecosystem for use with platforms like Claude Desktop.9 npm-
- FlicenseNot gradedqualityNot gradedmaintenanceA basic Model Context Protocol server implementation that demonstrates core MCP functionality including tools and resources. Provides weather alerts through the Weather API and serves as a learning example for MCP development.-
- FlicenseNot gradedqualityDmaintenanceA lightweight Model Context Protocol (MCP) server that gives AI assistants the ability to fetch real-time weather data for any city using the OpenWeatherMap API.1-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI assistants and LLMs to access real-time weather data and forecasts by connecting to the OpenWeatherMap API.-
- FlicenseNot gradedqualityDmaintenanceThis is a Model Context Protocol (MCP) server that provides weather information using the National Weather Service (NWS) API. Features Get weather alerts for a US state Get weather forecast for a specific location (using latitude and longitude)-
- AlicenseBqualityFmaintenanceA simple Model Context Protocol server that provides real-time weather data to AI agents like GitHub Copilot, allowing users to get current weather information for any city through natural language queries.216 npm97MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_alerts retrieves weather alerts for a U.S. state, while get_forecast provides forecast data for a specific latitude/longitude location. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun naming pattern (get_alerts, get_forecast) with identical verb usage and snake_case formatting. The naming is perfectly predictable and readable.
With only 2 tools for a weather server, the surface feels too thin for the domain. A weather service typically needs more operations like current conditions, historical data, or multi-day forecasts to be useful for agents. The count is borderline insufficient.
The tool set is severely incomplete for a weather domain. It lacks core operations like getting current conditions, historical weather data, or multi-location forecasts. Agents will hit dead ends trying to perform basic weather-related tasks with only alerts and single-location forecasts.