🌦️ Weekly Weather MCP Server

Connect 🌦️ Weekly Weather to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Weather MCP server which returns 7 days of detailed weather forecasts anywhere in the world. The 🌦️ weekly weather mcp server is what makes that connection.

What the server does

Animation showing Claude Desktop processing the weather data from the MCP Server

The One Call API 3.0 provides comprehensive weather data: - Current weather conditions - Minute forecast for 1 hour - Hourly forecast for 48 hours - Daily forecast for 8 days (including today) - National weather alerts - Historical weather data

• 🌍 Support for querying weather conditions anywhere in the world
• 🌤️ Hourly forecasts for the next 48 hours
• 📅 Provides detailed 8-day forecasts (today + following 7 days), with morning, afternoon, and evening data points
• 🌧️ Weather summaries and precipitation probabilities
• 🌡️ Detailed weather information including temperature, humidity, wind speed, etc
• 📍 Support for reporting results in different time zones

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Billing — Any calls beyond the free 1,000/day will be charged according to OpenWeatherMap pricing
• location — Location name as a string, e.g., “Beijing”, “New York”, “Tokyo”. The tool will handle geocoding this to a latitude/longitude coordinate
• api_key — OpenWeatherMap API key (optional, will read from environment variable if not provided)
• timezone_offset — Timezone offset in hours, e.g., 8 for Beijing, -4 for New York. Default is 0 (UTC time). Times in the returned data will be accurate for this
• get_weather — Get comprehensive weather data for a location including current weather (next 48 hours) and 8-day forecast with detailed information
• get_current_weather — Returns: - A simplified subset of the data returned by get_weather - Only the current weather information (temperature, feels like, weather
• Testing — This project includes unit tests, integration tests, and mock client test files to validate the MCP server functionality. The server has been

Credentials and setup notes

Configuration is passed through the environment: OPENWEATHER_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. 🌦️ Weekly Weather's toolset — Billing, location, api_key and 4 more — is a fair guide to whether it matches your workflow. It is maintained by rossshannon; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.