getHourlyWeather
Get hourly weather forecast for a location. Returns weather data hour by hour for the next 24 hours.
Current conditions, the coming days and the coming hours for a place resolved by name, ID or coordinates.
LABSCO SUMMARY
lookupCity accepts a name, an ID or coordinates and hands back a city ID the weather tools take, so the ambiguity lives in one place rather than in every request. The horizons are fixed rather than requested: getHourlyWeather covers the next 24 hours and getWeatherForecast the next few days, with each call taking a location and an options object. What comes back from getWeather is temperature, humidity and conditions — enough for a decision, not enough for a chart.
A weather server exposing 4 tools: current conditions, a daily forecast, an hourly forecast covering the next 24 hours, and a city lookup that returns the ID the weather calls accept.
No credentials are configured; a call needs a location, or a city ID obtained from lookupCity.
Add the configuration to your client
USE CASES
Pin down which city is meant, then read the coming days rather than only the present conditions.
Check what it is doing now, then look across the next 24 hours to pick the window.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
getHourlyWeatherGet hourly weather forecast for a location. Returns weather data hour by hour for the next 24 hours.
getWeatherGet current weather information for a location. Returns weather data including temperature, humidity, and conditions.
getWeatherForecastGet weather forecast for a location. Returns weather forecast for the next few days.
lookupCityLook up city information by name, ID, or coordinates. Returns city ID that can be used with other weather tools.
BEFORE YOU INSTALL
4 tools when we connected. Names are camelCase, such as getWeather and lookupCity; the WEATHER_* and QWEATHER_* variables set defaults and do not add tools.
CONTEXT COST
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
This one is configured rather than run — your client needs the configuration block, not a command.
{
"mcpServers": {
"mcp-weather-server": {
"command": "npx",
"args": [
"-y",
"mcp-weather-server"
]
}
}
}