# Arcgis Eagan [Health: Active]

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

## Description
City of Eagan GIS — Eagan, Minnesota open geospatial data (ArcGIS).

## Tools
Capabilities this server exposes over MCP:

- **search_datasets** — Search City of Eagan 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-eagan": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-arcgis-eagan"]
  }
}
```

## Documentation

## What Arcgis Eagan MCP server does

Arcgis Eagan MCP server exposes City of Eagan GIS data for use by MCP-compatible clients and applications. The source covers open geospatial datasets from Eagan, Minnesota, including parcels, zoning, public works, and city services.

The Arcgis Eagan MCP server is intended for discovery and read-oriented data access. An agent can search the available catalog, identify a relevant ArcGIS service URL, inspect its schema, and retrieve matching layer records. Results can include attributes and geometry, depending on the queried layer and requested fields.

This listing belongs to the Location Services category and is most relevant when an application needs local Eagan geographic data rather than a general-purpose map or geocoding service.

## How it works

Start with `search_datasets` and provide a keyword such as `parcels` or `zoning`. The response includes a dataset name, summary, record count, owner or organization, and a Feature Service URL. Pass that URL to the other tools.

Use `layer_info` to inspect a Feature Service or Map Service layer before querying it. The response describes field names and types, geometry type, total records, and service capabilities. Then call `query_layer` with the layer URL and optional query parameters. Supported controls include a SQL-like `where` expression, selected `out_fields`, `order_by`, `limit`, and `offset`. A `where` value of `1=1` with `out_fields` set to `*` can be used to sample a layer.

The gateway endpoint is available at `https://gateway.pipeworx.io/arcgis-eagan/mcp`. The gateway also exposes shared Pipeworx meta-tools, so its tool list contains more than the three ArcGIS-specific tools. A local stdio installation exposes only this pack's tools.

## Setup and configuration

For a remote connection, add the gateway URL to an MCP client configuration. The README specifically shows Claude Desktop, Cursor, and Windsurf as examples.

For local use, run the package with `npx -y @pipeworx/mcp-arcgis-eagan` and configure the MCP client to start that command. The local process communicates over stdin and stdout and does not require a Pipeworx account or gateway round-trip.

The tools can also be called over HTTP. For example, the gateway exposes a POST endpoint for `arcgis_eagan_search_datasets`, accepting a JSON request such as `{\"query\":\"parcels\",\"limit\":20}`.

## Tools and capabilities

- `search_datasets`: Finds Eagan GIS datasets by keyword and returns identifying metadata plus a service URL.
- `query_layer`: Retrieves attribute rows and geometry from an ArcGIS Feature Service or Map Service layer.
- `layer_info`: Reports a layer's fields, geometry type, record count, and capabilities.

The Arcgis Eagan MCP server can be used directly through these tools or indirectly with the gateway's `ask_pipeworx` tool, which accepts a plain-English question and routes it to an appropriate tool.

## Limitations and notes

Queries require a service URL, normally obtained from `search_datasets`. The available data is limited to the City of Eagan GIS sources represented by the service catalog.

Gateway connections include shared Pipeworx meta-tools in addition to the pack tools. If an application needs only the ArcGIS-specific surface, the standalone stdio package avoids those additional gateway tools. The exact gateway tool scope can change, and the connection's `initialize` response is the authoritative source for that scope.

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