Data360

What Data360 MCP server does

Data360 provides agent access to the World Bank Data360 platform, which brings together indicators from multiple source databases. Its main workflow is discovery first, retrieval second: identify an available database, search for an indicator, then request observations for a selected country or series.

The aggregated catalog includes sources such as World Development Indicators, IMF Balance of Payments, education statistics, WHO, and ILO series. Search results include indicator codes, names, database ownership, units, and definitions, helping an agent select the correct series before requesting values.

How it works

The server is available through the hosted endpoint at https://gateway.pipeworx.io/data360/mcp. MCP clients can connect to that URL directly. A full Pipeworx gateway endpoint is also available at https://gateway.pipeworx.io/mcp; both endpoints reach the same gateway and data sources, while the Data360 route lists this pack's tools directly.

A local npm package, @pipeworx/mcp-data360, acts as a stdio bridge. The client starts it with npx, and the bridge forwards requests to the hosted gateway, so the local option still needs network access. Direct HTTP calls are supported through the Pipeworx tools API, including POST requests to paths such as /v1/tools/data360_list_databases.

The scoped endpoint also exposes shared Pipeworx meta-tools. These include routing and discovery functions such as ask_pipeworx, which can select tools across the wider catalog. Set PIPEWORX_META_TOOLS=1 for the local bridge when those shared tools should be listed alongside the Data360 tools.

Setup and configuration

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

{
  "mcpServers": {
    "data360": {
      "url": "https://gateway.pipeworx.io/data360/mcp"
    }
  }
}

For the local stdio bridge, use:

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

Anonymous use is available with a daily limit of 50 calls. A free Pipeworx account increases the allowance to 200 calls; provide its key as PIPEWORX_API_KEY in the MCP server's environment. The key is sent as a Bearer token, and requests are metered under the gateway's billing model.

When running behind an HTTPS proxy, Node's built-in fetch does not automatically use HTTPS_PROXY. Newer Node releases can honor that variable when NODE_USE_ENV_PROXY=1 is set.

Tools and capabilities

• data360_list_databases returns source database IDs, names, and indicator counts. Use the returned ID to narrow later searches or data requests.
• data360_search_indicators performs full-text search across the unified indicator index. An optional database_id filter limits results to one source database.
• data360_get_data retrieves one series using a database ID, indicator code, and ISO3 country code. Results use SDMX-style fields such as OBS_VALUE, TIME_PERIOD, and UNIT_MEASURE, along with dimensions such as sex and age. Leaving out TIME_PERIOD requests the full series.
• ask_pipeworx can accept a plain-language question and route it to an appropriate gateway tool when the shared meta-tools are enabled or accessed through the gateway.

Limitations and notes

Data360 is an independent, unofficial integration and is not affiliated with, endorsed by, or published by the World Bank. The local bridge is a network client rather than an offline data package. Anonymous and account-based usage have different daily call limits, and the hosted connection can expose shared gateway tools in addition to the three Data360-specific tools.

The project is licensed under MIT.