MCP Weather

What TimLukaHorstmann/mcp-weather MCP server does

The TimLukaHorstmann/mcp-weather MCP server connects an MCP-compatible client to AccuWeather forecast data. It accepts a city or other location name and returns forecast information through two MCP tools: one for the next 12 hours and another for multi-day forecasts.

The server is intended for conversational weather lookups, such as checking whether rain is expected tomorrow, reviewing the weather for a trip, or asking for a forecast in a particular temperature system. Forecast results include weather information such as temperature, conditions, and precipitation details, according to the README.

How it works

The client starts the server locally, typically through the npm package runner. The server reads an AccuWeather API key from the ACCUWEATHER_API_KEY environment variable and uses that credential to request forecast data. A tool call supplies the location and, where supported, the desired units or forecast length.

Hourly requests return data for the next 12 hours. Daily requests can cover 1, 5, 10, or 15 days, with 5 days as the default. Metric output uses Celsius, while imperial output uses Fahrenheit. The README also describes an HTTP/REST arrangement using supergateway, but that is an optional wrapper around the server rather than a separate weather capability.

Setup and configuration

Running the TimLukaHorstmann/mcp-weather MCP server requires Node.js 18 or newer and an AccuWeather API key. AccuWeather provides a free tier, and the key must be exported in the shell or supplied in the MCP client configuration.

The documented direct launch command is:

npx -y @timlukahorstmann/mcp-weather

For a local client such as Claude Desktop, configure npx as the command, pass -y @timlukahorstmann/mcp-weather as its arguments, and set ACCUWEATHER_API_KEY in the server's environment. The repository also documents a source setup: clone the project, run npm install, create a .env file containing the key, and build with npm run build.

Tools and capabilities

• weather-get_hourly: accepts a required location and optional units. It returns the next 12 hours of forecast data.
• weather-get_daily: accepts a required location, optional days, and optional units. The supported day counts are 1, 5, 10, and 15; the default is 5.
• Unit selection supports metric for Celsius and imperial for Fahrenheit.
• Forecast responses can include temperatures, conditions, and precipitation information.

Limitations and notes

The server depends on the AccuWeather API and therefore cannot operate without an AccuWeather API key. Hourly coverage is limited to 12 hours, while daily coverage is limited to the supported forecast lengths and a maximum of 15 days. The README lists weather alerts, historical data, longer hourly windows, and location autocomplete as future enhancements, so those capabilities should not be assumed to be available currently.

The documented client configuration specifically covers Claude Desktop and describes the server as usable with other MCP-compatible clients. No weather alert or historical-weather tool is listed.