Arcgis Albuquerque

What Arcgis Albuquerque does

Arcgis Albuquerque gives AI agents access to open geospatial data published by the City of Albuquerque, New Mexico. Its coverage includes datasets related to parcels, zoning, public works, and city services. The server is an independent integration and is not affiliated with, endorsed by, or published by the City of Albuquerque or ArcGIS.

The workflow is designed for progressive discovery: find relevant datasets first, inspect a layer's structure when needed, then retrieve records from the resulting service URL. Returned query data can include attributes and geometry, making the server suitable for applications that need structured local GIS information rather than only dataset descriptions.

How it works

The hosted MCP endpoint is available at https://gateway.pipeworx.io/arcgis-albuquerque/mcp. Add that URL to an MCP client for a remote connection. The same Pipeworx gateway also exposes a broader endpoint at https://gateway.pipeworx.io/mcp; the pack-specific URL lists this pack's tools directly while also including shared gateway meta-tools.

A local package is available through npm and communicates over standard input and output. Run it with npx -y @pipeworx/mcp-arcgis-albuquerque, or configure the command in an MCP client. The local process exposes only the Arcgis Albuquerque tools, without the gateway's shared meta-tools or cross-catalog routing.

The gateway also offers HTTP tool calls, including a POST endpoint for dataset search at https://gateway.pipeworx.io/v1/tools/arcgis_albuquerque_search_datasets. Initial gateway calls do not require an account. Plain-language requests can be routed through the gateway's ask_pipeworx tool.

Setup and configuration

For a remote MCP connection, add an entry such as:

{
  "mcpServers": {
    "arcgis-albuquerque": {
      "url": "https://gateway.pipeworx.io/arcgis-albuquerque/mcp"
    }
  }
}

For local stdio execution, use:

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

No environment variables are required by the documented setup. The package can also be started directly with the same npx command to verify that it launches.

Tools and capabilities

• search_datasets searches Albuquerque GIS datasets by keyword. Results include the dataset name, summary, record count, owning organization, and a Feature Service URL.
• query_layer reads a Feature Service or Map Service layer using its URL. It accepts a SQL-like where condition, selected fields, ordering, a row limit, and an offset. Results contain attribute rows and geometry.
• layer_info reports a layer's fields and data types, geometry type, total record count, and supported capabilities.

A typical investigation starts with search_datasets, passes a returned URL to layer_info, and then uses query_layer with the appropriate fields and filter. To sample a layer broadly, use where set to 1=1 and out_fields set to *, subject to the service's available data and query behavior.

Limitations and notes

The gateway pack endpoint lists the three pack-specific tools alongside shared Pipeworx meta-tools, so its tool list is larger than the local package's list. The gateway's initialization response defines the exact scope exposed at connection time. The local stdio mode avoids those shared tools and provides only this pack's capabilities.

Queries depend on the ArcGIS service URL and layer schema. Use the dataset search result to obtain a relevant URL, and inspect it with layer_info before constructing more specific queries. The integration provides access to Albuquerque GIS data; it does not describe a general-purpose ArcGIS catalog beyond the connected city datasets.