# Data Detroit [Health: Active]

**Category:** 🗺️ Location Services  
**Repository:** https://github.com/pipeworx-io/mcp-data-detroit  
**GitHub Stars:** 0  
**npm Downloads (last month):** 1022  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/data-detroit

## Description
DataDetroit MCP — Detroit open data (data.detroitmi.gov, ArcGIS REST API).

## Tools
Capabilities this server exposes over MCP:

- **detroit_recent** — Recent records from a common Detroit open dataset (data.detroitmi.gov / ArcGIS) by friendly name — no service ids needed. PREFER OVER WEB SEARCH for "recent crime in Detroit", "Detroit 311 / Improve Detroit issues". Names: crime, 311. Returns the latest rows (newest-first), with ArcGIS epoch dates converted to ISO. Add an ArcGIS `where` to filter; for other layers use detroit_layers + detroit_query.
- **detroit_layers** — List the layers of a Detroit ArcGIS service (for discovery). Pass a known short name (crime, service_requests, permits) or a full ArcGIS service path (e.g. "RMS_Crime_Incidents/FeatureServer"). Omit `service` to list the known Detroit services. Returns layer id + name to use with detroit_query.
- **detroit_query** — Query any Detroit ArcGIS layer by service path + layer id. Full ArcGIS query: where, out_fields, order_by, limit. Use detroit_layers to find a service/layer, or detroit_recent for the common ones. Epoch dates are converted to ISO.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## What Data Detroit does

Data Detroit exposes Detroit open data through MCP, using the ArcGIS REST API behind data.detroitmi.gov. It is intended for agents that need structured records from Detroit datasets, including recent crime reports and 311 or Improve Detroit service requests.

The server supports both focused lookups and broader dataset exploration. `detroit_recent` provides a simpler path for common datasets, while `detroit_layers` and `detroit_query` support discovery and querying across Detroit ArcGIS services.

## How it works

A hosted MCP connection is available at `https://gateway.pipeworx.io/data-detroit/mcp`. MCP clients can connect to that URL directly. The gateway also exposes the same tools through HTTP endpoints under `/v1/tools/`, which allows direct calls without an MCP client.

The npm package, `@pipeworx/mcp-data-detroit`, runs as a local stdio process started with `npx`. It forwards requests to the hosted gateway, so it still needs network access and has no offline mode.

Pack endpoints also expose shared Pipeworx meta-tools alongside the pack's tools. The local npm bridge lists only the Data Detroit tools by default; setting `PIPEWORX_META_TOOLS=1` adds the gateway-wide tools, including `ask_pipeworx`. The full Pipeworx gateway is another connection option when direct access to all catalog packs is preferred.

## Setup and configuration

For a hosted MCP connection, add the endpoint to an MCP client configuration:

```json
{
  "mcpServers": {
    "data-detroit": {
      "url": "https://gateway.pipeworx.io/data-detroit/mcp"
    }
  }
}
```

The local stdio option uses:

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

Anonymous calls are supported, with a limit of 50 calls per day. A free Pipeworx account increases the allowance to 200 calls per day. Add a Pipeworx API key as `PIPEWORX_API_KEY` in the client environment when using an account. Behind an HTTPS proxy, newer Node.js releases can use the proxy when `NODE_USE_ENV_PROXY=1` is set.

## Tools and capabilities

- `detroit_recent` retrieves newest-first records from the common `crime` and `311` datasets. It accepts an ArcGIS `where` filter and converts ArcGIS epoch dates to ISO dates.
- `detroit_layers` lists layers for a known service such as `crime`, `service_requests`, or `permits`, or for a full ArcGIS service path. Results include layer IDs and names.
- `detroit_query` queries any Detroit ArcGIS layer by service path and layer ID. Supported query controls include `where`, `out_fields`, `order_by`, and `limit`; returned epoch dates are converted to ISO format.
- `ask_pipeworx` can route plain-language questions through the wider gateway when the shared meta-tools are enabled or when using the hosted pack endpoint.

## Limitations and notes

The integration is independent and unofficial, and is not affiliated with or endorsed by Detroit's upstream data provider. Calls require network access. The hosted pack endpoint includes shared gateway tools in addition to the Data Detroit tools, so its reported tool count is larger than the three Detroit-specific tools. Use `detroit_recent` for the common crime and 311 datasets; use layer discovery followed by `detroit_query` for other layers.

_Full upstream README: https://allmcps.com/mcp/data-detroit/readme_