data-detroit
Provides access to Detroit open data via the ArcGIS REST API, enabling queries and retrieval of geographic and tabular datasets from data.detroitmi.gov.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@data-detroitshow me the latest crime data for downtown Detroit"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-data-detroit
DataDetroit MCP — Detroit open data (data.detroitmi.gov, ArcGIS REST API).
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
Tool | Description |
| 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 |
| 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 |
| 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. |
Related MCP server: data-denver
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"data-detroit": {
"url": "https://gateway.pipeworx.io/data-detroit/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/data-detroit/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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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 Detroit data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides access to Cincinnati open data via the Socrata SODA API, allowing users to query datasets using natural language or direct tool calls.11MIT
- AlicenseNot gradedqualityCmaintenanceAccess and query Denver open geospatial data via the ArcGIS REST API, enabling natural language questions about Denver's datasets.14MIT
- AlicenseNot gradedqualityCmaintenanceAccess Baltimore open data (data.baltimorecity.gov) via ArcGIS REST API, enabling querying and retrieval of city datasets through natural language or direct tool calls.14MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and querying Durham, North Carolina open geospatial data from ArcGIS Feature/Map Services, including parcels, zoning, and public safety datasets via natural language or direct tool calls.14MIT
Related MCP Connectors
City of Detroit GIS — Detroit, Michigan open geospatial data (ArcGIS).
DataDC MCP — Washington, DC open data (opendata.dc.gov, ArcGIS REST API).
DataDenver MCP — Denver open data (opendata-geospatialdenver.hub.arcgis.com, ArcGIS REST API).
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pipeworx-io/mcp-data-detroit'
If you have feedback or need assistance with the MCP directory API, please join our Discord server