Provides tools for searching, querying, and inspecting ArcGIS feature services, specifically for City of Detroit open geospatial data (parcels, zoning, public works, etc.).
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., "@arcgis-detroit Search for parcels in Detroit with owner name 'Smith'"
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.
City of Detroit GIS — Detroit, Michigan open geospatial data (ArcGIS).
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tool | Description |
| Search City of Detroit GIS open geospatial datasets (parcels, zoning, public works & city services) by keyword. Returns each dataset's name, summary, record_count, owner/org, and its Feature Service |
| Query an ArcGIS Feature Service / Map Service layer by its url (from search_datasets). SQL-like |
| Get an ArcGIS Feature/Map Service layer's schema by url: fields (name + type), geometry type, total record count, and capabilities. |
Related MCP server: mcp-arcgis-dublinoh
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"arcgis-detroit": {
"url": "https://gateway.pipeworx.io/arcgis-detroit/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/arcgis-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.
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 Arcgis Detroit data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
DataDetroit MCP — Detroit open data (data.detroitmi.gov, ArcGIS REST API).
ArcGIS Hub — open government geospatial data (search + Feature Service query).
Search and query government open-data portals (Socrata SODA API).
DataDC MCP — Washington, DC open data (opendata.dc.gov, ArcGIS REST 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-arcgis-detroit'
If you have feedback or need assistance with the MCP directory API, please join our Discord server