Data Denver

What Data Denver does

Data Denver exposes Denver open-data records through MCP. The source is Denver’s ArcGIS-based open-data portal at opendata-geospatialdenver.hub.arcgis.com. Agents can inspect available services and layers, query a selected layer, or request recent records from supported friendly-name datasets.

The crime dataset is the documented friendly-name example and represents Denver Police offenses. Results from ArcGIS are returned with epoch-based date values converted to ISO-formatted dates, making them easier for agents and applications to interpret.

This is an independent, unofficial integration. It is part of the Pipeworx gateway, which provides access to multiple data-source packs.

How it works

A hosted MCP connection is available at:

https://gateway.pipeworx.io/data-denver/mcp

The endpoint exposes the three Data Denver tools and also includes shared Pipeworx meta-tools. The pack-specific endpoint lists Data Denver’s tools directly, while the full gateway endpoint at https://gateway.pipeworx.io/mcp lists tools from the broader catalog. The ask_pipeworx meta-tool can route natural-language requests across the catalog from either connection.

For applications that do not use an MCP client, the gateway also exposes HTTP tool calls. For example, a client can send a JSON POST request to /v1/tools/denver_recent with {"dataset":"crime"}.

The npm package, @pipeworx/mcp-data-denver, provides a local stdio process that forwards requests to the hosted gateway. It requires network access and has no offline mode.

Setup and configuration

Add the hosted endpoint to an MCP client as a remote server:

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

For a local stdio connection, configure the npm bridge:

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

Anonymous use is available with a limit of 50 calls per day. A free Pipeworx account raises the limit to 200 calls per day. Add PIPEWORX_API_KEY to the stdio server’s environment configuration to authenticate with an account key. Set PIPEWORX_META_TOOLS=1 if the local bridge should also list the shared gateway tools. The API key is sent as a Bearer token, and requests are metered through Pipeworx.

Tools and capabilities

• denver_recent retrieves the newest records for a friendly-name dataset. It supports an ArcGIS where filter and is intended for common recent-data requests such as Denver crime records.
• denver_layers lists layer IDs and names for a known short name or a full ArcGIS service path. Without a service argument, it lists known Denver services.
• denver_query queries any Denver ArcGIS layer using a service path and layer ID. Supported query controls include where, out_fields, order_by, and limit.

Use denver_layers when the required service or layer is unknown, then pass its results to denver_query. Use denver_recent for the documented common dataset path. Both record-oriented tools convert ArcGIS epoch dates to ISO format.