Openmeteo MCP Server

Most developer tooling work still happens through a UI a human drives. Openmeteo MCP server moves it into the conversation instead. A Model Context Protocol (MCP) server that provides access to weather data and forecasts through the OpenMeteo API. This server enables AI assistants to retrieve current weather conditions, forecasts, historical weather data, and search.

The short version

• Current Weather — Get real-time weather conditions including temperature, humidity, precipitation, wind, and atmospheric pressure
• Weather Forecasts — Retrieve detailed weather forecasts for up to 16 days
• Historical Weather — Access historical weather data for analysis and comparison
• Location Search — Find coordinates and details for cities and locations worldwide
• Free API — Uses the free OpenMeteo API with no API key required
• Comprehensive Data — Includes temperature, precipitation, wind, pressure, cloud cover, and weather descriptions

The tools it exposes

The server publishes 1 tool. What each one is for:

• Prerequisites — The Prerequisites tool exposed by this server

Getting it running

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

What it needs from you

• Rust 1.87 or newer - Cargo package manager

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Openmeteo's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by gbrigandi; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Openmeteo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• 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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.