mcp-worldbank-climate
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-worldbank-climateshow me annual rainfall data for Kenya from 2000 to 2020"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-worldbank-climate
World Bank Climate Change Knowledge Portal (CCKP) MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
Tool | Description |
| World Bank CCKP climate data for any country: historical observations and CMIP6 climate-model projections. Returns mean temperature, max/min temperature, or precipitation, by emissions scenario. Pass the components as separate args — this tool assembles the brittle composite "indicator code" for you. Values are returned keyed by ISO3 country code; the inner key is "-07" (annual/period) or per-season months.nnWORKED EXAMPLES (all verified live):n1. Historical annual mean temperature for the USA (defaults): {"geography":"USA"} => tas climatology over 1995-2014, ~10.2°C.n2. Projected warming (anomaly) for the USA mid-century under a high scenario: {"geography":"USA","scenario":"ssp585","period":"2040-2059","product":"anomaly"} => ~2.4°C above baseline.n3. Historical annual precipitation for all countries: {"geography":"all_countries","variable":"pr","product":"climatology","period":"1995-2014","scenario":"historical"} => mm/year per country.nnIf assembly ever fails for an exotic combination, pass the full composite string via indicator_code instead. |
| Return a static reference object documenting all verified CCKP indicator-code components: valid variables (tas/tasmax/tasmin/pr), scenarios (historical + SSP119–585), periods, products (climatology/anomaly), aggregations (annual/seasonal), and the 11-token composite code order. Takes no arguments; call before get_climate_data to choose valid parameter combinations.Call this to learn valid variables, scenarios, periods, products, and aggregations before building a get_climate_data request. Takes no arguments. |
Related MCP server: mcp-openweather
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"worldbank-climate": {
"url": "https://gateway.pipeworx.io/worldbank-climate/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/worldbank-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.
Using with ask_pipeworx
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 Worldbank Climate data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Let AI agents query data and act across all your business apps via MCP.
The official Model Context Protocol server for Ambee. It gives any MCP-compatible AI assistant — Claude, ChatGPT, Cursor, VS Code, Ollama, and more direct access to live air quality, pollen, and weather data. To get started, including information on signing up and obtaining your Ambee key, check out the Ambee documentation on https://docs.ambeedata.com
Interact with climate metrics via Riskthinking.AI's CDT Express API in supported AI chat experiences
OpenWeather data for AI agents: list feeds, sign up, check balance, get a top-up link, fetch data.
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables AI agents to retrieve real-time weather conditions and forecasts via OpenWeatherMap API. Supports interactive weather queries and travel planning through MCP tools, resources, and prompts.2-
- AlicenseNot gradedqualityCmaintenanceWraps the OpenWeatherMap API to provide weather data through MCP, enabling AI agents to query current conditions, forecasts, and other weather information via natural language.5 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides weather data from WeatherAPI.com through MCP, enabling AI agents to query current conditions and forecasts via natural language.5 npmMIT
- FlicenseNot gradedqualityDmaintenanceExposes World Bank development data and country information via MCP resources and tools, enabling AI agents to query historical indicators and live API data.-