mcp-norwegian-weather
# mcp-norwegian-weather 🇳🇴🌤️
MCP server for Norwegian weather data using **MET Norway Locationforecast 2.0** (the API behind yr.no).
## Tools
- **current_weather** — Current conditions for any Norwegian location
- **weather_forecast** — Hourly forecast up to 72 hours ahead
## Features
- 30+ built-in Norwegian cities (Oslo, Bergen, Tromsø, Lofoten, Svalbard...)
- Geocoding fallback for any Norwegian location
- Coordinate input support (lat,lon)
- MET Norway's symbol codes mapped to readable descriptions
## Usage
```json
{
"mcpServers": {
"norwegian-weather": {
"command": "node",
"args": ["/path/to/mcp-norwegian-weather/src/index.js"]
}
}
}
```
## Data Source
[MET Norway Locationforecast 2.0](https://api.met.no/weatherapi/locationforecast/2.0/documentation) — free, requires User-Agent identification (included). Powers yr.no, one of the world's most accurate weather services.
## Part of the Nordic MCP Suite
This is one of several Nordic MCP servers. See [mcp-nordic](https://github.com/robobobby/mcp-nordic) for the unified meta-server.
## License
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.