# Arcgis Charlotte [Health: Active]

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

## Description
City of Charlotte GIS — Charlotte, North Carolina open geospatial data (ArcGIS).

## Tools
Capabilities this server exposes over MCP:

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

## Documentation

## What Arcgis Charlotte MCP server does

Arcgis Charlotte provides MCP access to the City of Charlotte, North Carolina's open geospatial datasets. The source data is delivered through ArcGIS Feature Services and Map Services. Available coverage includes examples such as parcels, zoning, public works, and city services, with dataset discovery based on keywords.

The Arcgis Charlotte MCP server is an independent, unofficial integration. It is not affiliated with, endorsed by, or published by the City of Charlotte or another upstream provider. Use it when an AI agent needs to identify relevant Charlotte GIS data and then retrieve records from the corresponding ArcGIS layer.

## How it works

The normal workflow begins with `search_datasets`. A keyword search returns matching dataset names, summaries, record counts, owning organization information, and a Feature Service URL. That URL is then supplied to `layer_info` to understand the layer before querying it, or directly to `query_layer` when the required layer is already known.

`query_layer` accepts SQL-like filtering through `where`, a comma-separated list of requested fields through `out_fields`, ordering through `order_by`, and pagination using `limit` and `offset`. Results contain attribute rows and geometry. To inspect a sample, use `where` set to `1=1` and `out_fields` set to `*`.

## Setup and configuration

The Arcgis Charlotte MCP server can be connected through the Pipeworx gateway at `https://gateway.pipeworx.io/arcgis-charlotte/mcp`. A standard MCP client configuration uses that URL as the server endpoint. The gateway connection exposes the pack's three tools and also includes shared Pipeworx meta-tools; the exact scope is reported by the connection's `initialize` response.

For a local installation, run the package with `npx -y @pipeworx/mcp-arcgis-charlotte` and configure it as a stdio MCP server. This local mode does not require a Pipeworx account or gateway round-trip and exposes only the pack's own tools. The same package can be started directly with npx to verify that it launches.

The gateway also provides HTTP tool access. For example, the dataset search tool can be called at `https://gateway.pipeworx.io/v1/tools/arcgis_charlotte_search_datasets` with a JSON query. The provided setup notes state that an account is not needed for the first calls.

## Tools and capabilities

- `search_datasets`: Finds City of Charlotte GIS datasets by keyword and returns metadata plus a service URL.
- `query_layer`: Retrieves filtered ArcGIS layer records, including attributes and geometry, with field selection, sorting, limits, and offsets.
- `layer_info`: Reports a layer's fields and types, geometry type, total record count, and capabilities.

Together, these tools support dataset discovery, schema inspection, and targeted record retrieval without requiring an agent to know the ArcGIS service URL in advance.

## Limitations and notes

The Arcgis Charlotte MCP server is limited to the City of Charlotte GIS datasets exposed through the integration. Search results and layer contents depend on the available upstream ArcGIS services. The gateway endpoint includes additional shared Pipeworx tools beyond the three pack tools, whereas local stdio mode does not.

The integration is unofficial, and the gateway's tool scope may change; its `initialize` response is the authoritative source for the current connection. The material does not describe authentication settings, environment variables, refresh behavior, or guarantees about dataset freshness.

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