World Development Indicators MCP server
{
"mcpServers": {
"daedalmap-world-development-indicators": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/world_bank_wdi"
}
}
}{
"mcpServers": {
"daedalmap-world-development-indicators": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/world_bank_wdi"
}
}
}{
"mcpServers": {
"daedalmap-world-development-indicators": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/world_bank_wdi"
}
}
}{
"servers": {
"daedalmap-world-development-indicators": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/world_bank_wdi"
}
}
}{
"mcpServers": {
"daedalmap-world-development-indicators": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/world_bank_wdi"
}
}
}What it does
DaedalMap is a geographic query engine that provides access to World Bank World Development Indicators and 40+ other curated data sources on disasters, demographics, economics, and climate. It is available as a hosted MCP server or can be self-hosted, letting developers query and join geographic and indicator data using plain language.
- Query World Bank development indicators (health, education, economy) for specific countries and years to build analyses or reports.
- Combine disaster event data (earthquakes, hurricanes, floods) with economic and health indicators to compare impact context across regions and time periods.
- Transform and align geographic data using stable location identifiers (loc_id), then join it with maintained data packs for integrated analysis.
Tools this server exposes
| Tool | Does |
|---|---|
| get_catalog | Discover current data packs available in the system. |
| read_geometry_catalog | Check current geometry coverage across supported geographic references. |
| help | Guided onboarding and documentation for using DaedalMap tools. |
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.