
Wraps the Open-Meteo Climate API and makes it accessible through MCP without requiring authentication. Part of the Pipeworx gateway platform that bundles 673+ data sources behind a unified interface. You can connect directly to this single climate endpoint or use the full Pipeworx gateway to access the entire catalog. The ask_pipeworx tool lets you query in natural language instead of calling specific endpoints, which is handy when you're prototyping climate data integrations or building agents that need weather and climate information. Ships over streamable HTTP, so it works with Claude Desktop and similar MCP clients out of the box.
Climate MCP — wraps Open-Meteo Climate API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
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. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"climate": {
"url": "https://gateway.pipeworx.io/climate/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/climate/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Climate data" })
The gateway picks the right tool and fills the arguments automatically.
MIT