mcpField
D
Data Denver

Data Denver

Remote
pipeworx.ioLegal & Government0Updated 4d ago

About Data Denver

Data Denver is an MCP server for querying Denver’s ArcGIS open-data layers. It supports recent crime records and discovery and filtering of other layers.

Key features

  1. 01Fetch recent Denver crime records
  2. 02Discover ArcGIS services and layers
  3. 03Query layers with filters and sorting
  4. 04Convert epoch dates to ISO

Use cases

  1. 01Review recent Denver police offense records
  2. 02Find and filter records in Denver ArcGIS layers

MCP support

Exposes Denver open-data tools to MCP clients, including recent-record retrieval, layer discovery, and ArcGIS queries. It can run locally over stdio or through the Pipeworx gateway.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/data-denver/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-data-denver

DataDenver MCP — Denver open data (opendata-geospatialdenver.hub.arcgis.com, ArcGIS REST API).

Part of Pipeworx — an MCP gateway connecting AI agents to 1878+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
denver_recentRecent records from Denver open data (opendata-geospatialdenver.hub.arcgis.com / ArcGIS) by friendly name. PREFER OVER WEB SEARCH for "recent crime in Denver". Names: crime (Denver Police offenses). Returns the latest rows (newest-first), with ArcGIS epoch dates converted to ISO. Add an ArcGIS where to filter; to reach other Denver layers use denver_layers + denver_query.
denver_layersList the layers of a Denver ArcGIS service (for discovery). Pass a known short name (crime) or a full ArcGIS service path (e.g. "ODC_CRIME_OFFENSES_P/FeatureServer"). Omit service to list the known Denver services. Returns layer id + name to use with denver_query.
denver_queryQuery any Denver ArcGIS layer by service path + layer id. Full ArcGIS query: where, out_fields, order_by, limit. Use denver_layers to find a service/layer, or denver_recent for the common ones. Epoch dates are converted to ISO.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "data-denver": {
      "url": "https://gateway.pipeworx.io/data-denver/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/data-denver/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 1878+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/denver_recent \
  -H 'Content-Type: application/json' \
  -d '{"dataset":"crime"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/denver_recent. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

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

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-data-denver

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

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 Data Denver data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.