# Arcgis Albuquerque [Health: Active]

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

## Description
City of Albuquerque GIS — Albuquerque, New Mexico open geospatial data (ArcGIS).

## Tools
Capabilities this server exposes over MCP:

- **search_datasets** — Search City of Albuquerque 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 `url` — pass that url to query_layer / layer_info.
- **query_layer** — Query an ArcGIS Feature Service / Map Service layer by its url (from search_datasets). SQL-like `where`, comma-separated `out_fields`, `order_by`, `limit`, `offset`. Returns attribute rows (and geometry). Use where="1=1" + out_fields="*" to sample.
- **layer_info** — Get an ArcGIS Feature/Map Service layer's schema by url: fields (name + type), geometry type, total record count, and capabilities.

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

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

## Documentation

## 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:

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

For local stdio execution, use:

```json
{
  "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.

_Full upstream README: https://allmcps.com/mcp/arcgis-albuquerque/readme_