Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@KNMI MCP Server what's the weather forecast for Amsterdam this weekend?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server that provides access to Dutch weather data via the KNMI (Royal Netherlands Meteorological Institute) API.
This MCP server enables AI assistants and applications to access comprehensive Dutch weather information, including current conditions, forecasts, alerts, and historical data. It automatically handles location name resolution, converting human-readable Dutch city names into KNMI grid identifiers.
Related MCP server: mcp-swedish-weather
get_weatherGet comprehensive weather information for any Dutch location.
Parameters:
location (string, required): Dutch location name (e.g., "Amsterdam", "De
Bilt"). Will (fuzzy) matched to a well-known/mapped locality.
region (number, optional): Region number (0-15) for additional regional
context
Returns:
Current weather conditions and temperature
Hourly forecast (next 48 hours)
Daily forecast (next 7 days)
Weather alerts and warnings
Wind conditions (speed, direction, gusts)
Precipitation data (amount, chance)
UV index information
Sunrise and sunset times
Weather backgrounds for visual representation
Add to your MCP host configuration (e.g. Claude Desktop, VS Code, etcetera):
{
"knmi-weather": {
"command": "npx",
"args": ["-y", "@dstotijn/knmi-mcp"]
}
}Temperature (°C)
Weather type code
Wind speed, direction, and gusts
Precipitation amount and probability
UV index with safety recommendations
Hourly: Next 48 hours with detailed conditions
Daily: Next 7 days with min/max temperatures and precipitation
Alert levels: none, potential, yellow, orange, red
Detailed descriptions and safety advice
Affected regions and time periods
Sunrise and sunset times
Weather backgrounds for UI visualization
Regional weather information
Historical climate data context
©️ 2025 David Stotijn
Get current weather information for a Dutch location. The location parameter accepts location names (e.g., 'Amsterdam', 'De Bilt') and automatically converts them to the required grid identifiers.
Inputs: location (required), region. Returns: sun, wind, daily, alerts, +4 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'get_weather' has a clear and distinct purpose, making disambiguation trivial.
The single tool name 'get_weather' follows a clear verb_noun pattern (get + weather). Since there is only one tool, consistency is inherently perfect with no deviations to evaluate.
A single tool is too few for a weather server's apparent scope, which typically involves multiple operations like forecasts, historical data, or alerts. This minimal set limits functionality and feels incomplete for the domain.
The tool set is severely incomplete for a weather server, covering only current weather retrieval. Obvious gaps include forecasts, historical data, alerts, or multi-location queries, which are essential for comprehensive weather-related tasks.
Weather forecasts from MET Norway (Yr): geocoding plus hourly forecasts worldwide.
Global weather via Open-Meteo: forecast, historical, marine, air quality, geocoding, elevation.
Current weather and 7-day forecast for any place (MET Norway). $0.006/call via x402.
OpenWeather MCP — wraps the OpenWeatherMap API (openweathermap.org)