Data Gov Sg

What Data Gov Sg does

Data Gov Sg exposes Singapore open government data through MCP. The catalog spans approximately 2,000 datasets across areas such as population, the economy, transport, and the environment. It also provides live feeds for current conditions, including weather observations, air quality, UV levels, taxi availability, and expressway incidents.

The upstream source is the public, keyless data.gov.sg v2 API. The integration is independent and unofficial; it is not published, endorsed, or affiliated with the Singapore government data provider.

How it works

An MCP client can connect directly to the hosted pack endpoint:

{
  "mcpServers": {
    "data-gov-sg": {
      "url": "https://gateway.pipeworx.io/data-gov-sg/mcp"
    }
  }
}

The hosted endpoint runs through the Pipeworx gateway. Its tool list includes the Data Gov Sg tools and shared gateway meta-tools, such as ask_pipeworx, discover_tools, search_within, and memory-related tools. ask_pipeworx can route a plain-language question across the wider Pipeworx catalog, including from this scoped connection. A full gateway connection is also available when an agent should list all packs directly.

Clients without MCP support can call tools over HTTP. For example, the dataset search tool is available at POST https://gateway.pipeworx.io/v1/tools/data_gov_sg_search_datasets with a JSON request body.

Setup and configuration

The npm package, @pipeworx/mcp-data-gov-sg, provides a local stdio bridge. Configure an MCP client to start it with npx:

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

The bridge requires network access and has no offline mode. Anonymous use is capped at 50 calls per day. Setting PIPEWORX_API_KEY with a key from Pipeworx raises the allowance to 200 calls per day; authenticated calls use a Bearer token and are metered and billed as hosted calls. Set PIPEWORX_META_TOOLS=1 if the local bridge should also list the shared gateway tools. Proxy users may need NODE_USE_ENV_PROXY=1 for Node’s fetch implementation to honor HTTPS_PROXY.

Tools and capabilities

• search_datasets(query?, page?, page_size?) browses the catalog.
• get_dataset(dataset_id) returns dataset metadata and its schema.
• query_dataset(dataset_id, limit?, offset?, filters?) retrieves tabular rows.
• weather_now() reports temperature, humidity, wind, and rain across more than 50 stations.
• air_quality_psi() returns PSI readings for five regions.
• air_quality_pm25() returns PM2.5 readings.
• uv_index() provides the current UV index.
• taxi_availability() reports live taxi positions.
• traffic_incidents() returns current expressway incidents.

Limitations and notes

The local bridge forwards requests to the hosted gateway rather than running the data service locally. The public data source is keyless, but Pipeworx usage limits apply to anonymous and authenticated gateway calls. Pack endpoints always include shared Pipeworx meta-tools; use the local bridge without PIPEWORX_META_TOOLS, or connect to the full gateway when choosing a different tool-listing arrangement.