MCP Quickstart Weather Server
Related Servers
Alternatives to MCP Quickstart Weather Server
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.7 npm-
- FlicenseNot gradedqualityDmaintenanceA simple MCP server that provides weather tools, deployable with Docker, and designed to be used with Claude Desktop via a WSL bridge.-
- AlicenseNot gradedqualityBmaintenanceMCP server providing weather lookup, semantic search over personal notes (RAG), and image generation tools for any MCP client like Claude Desktop.MIT
- FlicenseNot gradedqualityDmaintenanceA training MCP server built with TypeScript that provides basic tools (add, get_weather) and a resource (favorite-cities) for use with Claude Desktop. Weather data is fetched from Open-Meteo without requiring an API key.-
- FlicenseNot gradedqualityDmaintenanceA proof-of-concept MCP server that provides weather information using the Open-Meteo API, with tools for greeting, getting weather by coordinates, and by location name.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps the Ambient Weather REST API. Query your personal weather stations conversationally from Claude Code, Claude.ai, or any MCP-compatible client.1MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_alerts retrieves alerts for a US state, while get_forecast provides forecasts for a specific latitude/longitude location. There is no overlap in functionality or ambiguity between them.
Both tools follow a consistent verb_noun naming pattern (get_alerts, get_forecast) with the same verb 'get' and descriptive nouns. The naming is predictable and uniform throughout the set.
With only 2 tools, the server feels thin for a weather domain. While it covers alerts and forecasts, it lacks other common weather operations like current conditions, historical data, or radar information, making the scope limited.
The tool surface is significantly incomplete for a weather server. It misses core functionalities such as getting current weather, historical data, or supporting broader geographic queries beyond US states or specific coordinates, which will limit agent effectiveness.