Log inSubmit server
Open Meteo logo

Open Meteo

Access forecasts, historical reanalysis, geocoding, air quality, marine, and flood data through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Open Meteo

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "open-meteo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-open-meteo"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @pipeworx/mcp-open-meteo

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 5d ago.

Overview

The Open Meteo MCP server exposes public Open-Meteo weather and environmental APIs through MCP. It provides forecast, historical reanalysis, geocoding, air-quality, marine, and flood tools, with gateway and local stdio deployment options. Use it when an AI agent needs location-based weather or related environmental data without API credentials. Public access is subject to a non-commercial fair-use limit of 10,000 requests per day per IP.

Use cases

  • Retrieve a multi-day forecast for a coordinate
  • Convert a place name into latitude and longitude
  • Query historical weather reanalysis for a date range
  • Check air quality, marine conditions, or river discharge

Key features

  • Up to 16-day weather forecasts
  • ERA5 historical reanalysis from 1940 onward
  • Place-name geocoding
  • Air quality, marine, and flood forecasts
  • Hosted MCP and local stdio modes

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @pipeworx/mcp-open-meteo (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads492Package downloads in the last 30 days.
Last commit25d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Open Meteo works

What the Open Meteo MCP server does

The Open Meteo MCP server gives MCP-compatible AI clients access to public Open-Meteo APIs for weather and environmental data. Its tools cover short-term forecasts, historical ERA5 reanalysis, place-name geocoding, air quality, marine conditions, and river discharge forecasts.

Forecast queries accept latitude and longitude and can request hourly or daily values, a forecast length of up to 16 days, and a timezone. Historical queries use a coordinate plus start and end dates and can return hourly or daily reanalysis data dating back to 1940. Geocoding converts a place name into coordinates, while the environmental tools provide particulate matter and gas forecasts, wave measurements, or GloFAS river discharge forecasts.

How it works

The Open Meteo MCP server can be reached through a hosted Pipeworx MCP endpoint or run locally as a package. The hosted pack URL exposes the Open-Meteo tools together with shared Pipeworx meta-tools. These include routing and discovery functions such as ask_pipeworx, which can send a broader question to other sources in the Pipeworx catalog. The endpoint's initialize response and tools/list response define the tools available at connection time.

A full Pipeworx gateway URL lists all available packs directly. Both hosted URLs use the same gateway and data sources; the pack endpoint simply lists this pack's tools directly while retaining the shared gateway tools.

The local process communicates over standard input and output using MCP. Unlike the hosted endpoint, it exposes only the Open-Meteo pack tools and does not include Pipeworx meta-tools or cross-catalog routing.

Setup and configuration

Add the hosted endpoint to an MCP client with the URL https://gateway.pipeworx.io/open-meteo/mcp. The README names Claude Desktop, Cursor, and Windsurf as supported client examples. No account is required for the initial hosted calls.

For local execution, configure the client to run npx -y @pipeworx/mcp-open-meteo, or launch that command directly to verify that the process starts. This mode does not require a Pipeworx account and avoids a gateway round trip. The package uses no documented environment variables or authentication settings.

Clients without MCP support can call the hosted HTTP interface directly. For example, a POST request to /v1/tools/open_meteo_forecast can submit latitude, longitude, units, and forecast-day parameters. Tool schemas can be inspected with the corresponding GET endpoint.

Tools and capabilities

  • forecast: Retrieves up to 16 days of forecast data by coordinate, with optional hourly, daily, forecast-length, and timezone parameters.
  • historical: Retrieves ERA5 reanalysis data for a coordinate and date range from 1940 onward.
  • geocode: Looks up coordinates from a place name, with optional result count and language settings.
  • air_quality: Queries global particulate matter, ozone, and nitrogen dioxide forecasts.
  • marine: Returns wave height and wave period data.
  • flood: Returns GloFAS river discharge forecasts.

Limitations and notes

The underlying public APIs do not require authentication, but usage is limited to non-commercial fair use. The stated limit is 10,000 requests per day per IP. Hosted pack connections include shared meta-tool schemas in addition to the pack's own tools, which increases the listed tool count. Use the local stdio mode when only the six Open-Meteo tools are needed, or use the full gateway when direct access to the broader catalog is preferable.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Open Meteo

Open Meteo is an MCP server that connects AI agents to public Open-Meteo weather APIs and exposes forecast, historical, geocoding, air-quality, marine, and flood tools. It requires no authentication and supports either a gateway URL or local stdio execution for weather and environmental data.

Run `npx -y @pipeworx/mcp-open-meteo` for local stdio execution, then add that command to your MCP client's server configuration. You can instead configure the hosted URL `https://gateway.pipeworx.io/open-meteo/mcp`, which does not require a local package or Pipeworx account for initial calls.

Yes, Open Meteo works with Cursor through the hosted MCP endpoint or the local stdio command. Add `https://gateway.pipeworx.io/open-meteo/mcp` as the server URL, or configure Cursor to run `npx -y @pipeworx/mcp-open-meteo`.

No, the Open-Meteo data sources require no authentication. Access remains subject to non-commercial fair use and a stated limit of 10,000 requests per day per IP.

Related MCP servers

All in Environment & Nature All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpen Meteo AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/open-meteo?style=directory)](https://allmcps.com/mcp/open-meteo)
HTML Embed
<a href="https://allmcps.com/mcp/open-meteo"><img src="https://allmcps.com/api/badge/open-meteo?style=directory" alt="Open Meteo on AllMCPs" /></a>