mcp-norwegian-weather
Related Servers
Alternatives to mcp-norwegian-weather
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides real-time weather data, hourly forecasts, and daily summaries using the free Open-Meteo API with no API key required. It enables users to search for weather conditions by specific coordinates or city names across multiple measurement units.2MIT
- AlicenseAqualityBmaintenanceAn MCP server that provides weather forecasts and current conditions for any city via the free Open-Meteo API, with no API key or account required.299 npmMIT
- AlicenseAqualityBmaintenanceMCP server for weather forecasts via Open-Meteo (no API key needed), providing current weather, hourly, and daily forecasts with geocoding support.3MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that provides real-time weather data and forecasts via Open-Meteo, with tools for current conditions, multi-day forecasts, umbrella predictions, and travel recommendations.-
- FlicenseNot gradedqualityBmaintenanceA minimal MCP server that provides current weather and forecasts for any city using the free Open-Meteo API, no API key required.13 npm-
- AlicenseNot gradedqualityDmaintenanceA cross-platform MCP server that provides weather forecasts by coordinates, location name, or IP address without requiring API keys. It leverages Open Meteo and OpenStreetMap to deliver fast, single-query weather lookups.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: current_weather retrieves current conditions, while weather_forecast provides hourly forecasts. There is no overlap or ambiguity between them, making it easy for an agent to select the appropriate tool based on the need for immediate vs. future weather data.
Both tools follow a consistent snake_case naming pattern with a clear 'noun_adjective' structure (current_weather, weather_forecast). The naming is predictable and readable, with no deviations or mixed conventions.
With only 2 tools, the server feels thin for a weather domain, as it lacks capabilities like historical data, alerts, or multi-day forecasts. While the tools cover basic current and forecast needs, the count is borderline minimal for comprehensive weather functionality.
The server provides core current and forecast operations but has notable gaps, such as missing historical weather data, severe weather alerts, or location search tools. Agents can work around this for basic queries, but the surface is incomplete for full weather domain coverage.