# climate [Health: Active]

**Category:** 🌳 Environment & Nature  
**Repository:** https://github.com/pipeworx-io/mcp-climate  
**GitHub Stars:** 0  
**npm Downloads (last month):** 450  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/climate

## Description
Climate MCP — wraps Open-Meteo Climate API (free, no auth)

## Tools
Capabilities this server exposes over MCP:

- **get_climate_projection** — Get historical and future temperature and precipitation projections for a location (1950–2050). Returns daily forecasts with temperature, precipitation, and weather conditions.
- **compare_models** — Compare temperature projections across climate models for the same location and date range. Returns side-by-side daily mean temperatures to assess model agreement and uncertainty.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "climate": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-climate"]
  }
}
```

## Documentation

## What climate does

climate exposes Open-Meteo Climate API data through the Model Context Protocol. It is intended for requests that need historical and projected climate information for a specific latitude, longitude, and date range. The supported projection period spans 1950–2050 and includes daily temperature, precipitation, and weather-condition results.

Two dedicated tools are available:

- `get_climate_projection` retrieves temperature and precipitation projections for a location, together with daily weather conditions.
- `compare_models` places temperature projections from multiple climate models side by side for the same location and date range, returning daily mean temperatures to help assess agreement and uncertainty.

The integration is independent and unofficial; it is not affiliated with, endorsed by, or published by Open-Meteo.

## How it works

The server can be used in two ways. A hosted MCP endpoint is available through Pipeworx at `https://gateway.pipeworx.io/climate/mcp`. This endpoint lists the climate tools along with shared Pipeworx gateway tools. Those shared tools include routing and discovery functions such as `ask_pipeworx`, which can direct a natural-language request across the broader catalog.

A local package is also available through npm as `@pipeworx/mcp-climate`. Running it with `npx` starts an MCP server over standard input and output. The local process exposes only the climate pack's tools and does not include the gateway's shared meta-tools.

Clients that cannot use MCP directly can call the gateway's HTTP tool endpoint. For example, `POST https://gateway.pipeworx.io/v1/tools/get_climate_projection` accepts a JSON request containing coordinates and a date range. The gateway also provides HTTP endpoints for inspecting tools and searching packs.

## Setup and configuration

For a hosted connection, add the following server entry to an MCP client:

```json
{
  "mcpServers": {
    "climate": {
      "url": "https://gateway.pipeworx.io/climate/mcp"
    }
  }
}
```

For a local stdio connection, use the npm package:

```json
{
  "mcpServers": {
    "climate": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-climate"]
    }
  }
}
```

You can verify the local process starts with `npx -y @pipeworx/mcp-climate`. The gateway connection does not require an account for initial calls, and the climate API integration requires no authentication. A full Pipeworx gateway endpoint is also available at `https://gateway.pipeworx.io/mcp` when direct access to all catalog packs is preferred.

## Tools and capabilities

### `get_climate_projection`

Request climate data for a location and date range. The response contains daily forecasts with temperature, precipitation, and weather conditions, covering historical and future projections within the supported 1950–2050 range.

### `compare_models`

Compare temperature projections from climate models for one location and date range. Results provide side-by-side daily mean temperatures, making it possible to inspect model agreement and variation.

## Limitations and notes

The hosted pack endpoint includes shared Pipeworx meta-tools in addition to the two climate tools, so its tool list is larger than the climate-specific set. The local stdio mode avoids those shared tools and exposes only the pack's own capabilities. Both modes use the same climate tools, but only the gateway offers cross-catalog routing through `ask_pipeworx`.

The server focuses on temperature, precipitation, weather conditions, and model comparison. It does not provide a general-purpose climate dataset interface beyond these listed operations.

_Full upstream README: https://allmcps.com/mcp/climate/readme_