# Arcgis Castateparks [Health: Active]

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

## Description
California State Parks GIS — California State Parks open geospatial data (ArcGIS).

## Tools
Capabilities this server exposes over MCP:

- **search_datasets** — Search California State Parks GIS open geospatial datasets (parks, trails, recreation & natural-resource layers) 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-castateparks": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-arcgis-castateparks"]
  }
}
```

## Documentation

## What Arcgis Castateparks MCP server does

The Arcgis Castateparks MCP server connects AI agents to California State Parks open GIS data published through ArcGIS. It focuses on datasets such as parks, trails, recreation areas, and natural-resource layers. The integration is an independent, unofficial connection and is not affiliated with the upstream provider.

Its workflow is designed around dataset discovery followed by layer access. A search returns dataset names, summaries, record counts, owning organization, and a Feature Service URL. That URL can then be used with the layer inspection and query tools.

## How it works

The Arcgis Castateparks MCP server provides three pack-specific tools:

- `search_datasets` finds California State Parks GIS datasets by keyword.
- `layer_info` reports a layer's fields and types, geometry type, record count, and capabilities.
- `query_layer` retrieves records from an ArcGIS Feature Service or Map Service layer.

A typical request starts with `search_datasets`, for example with a term related to trails. The returned service URL becomes the input for `layer_info` or `query_layer`. Queries support SQL-like `where` conditions, selected fields through comma-separated `out_fields`, ordering, limits, and offsets. Results include attribute rows and geometry. To sample a layer broadly, the documented pattern is `where="1=1"` with `out_fields="*"`.

## Setup and configuration

The Arcgis Castateparks MCP server can be added through the Pipeworx gateway with this streamable HTTP endpoint:

`https://gateway.pipeworx.io/arcgis-castateparks/mcp`

The gateway endpoint exposes the pack tools along with shared Pipeworx meta-tools, including routing and discovery functions. Its `initialize` response is the authoritative source for the tools available at a given time.

A local package is also available through npm and runs as a stdio MCP server:

`npx -y @pipeworx/mcp-arcgis-castateparks`

The standalone process exposes only this pack's tools and does not require a Pipeworx account.

## Tools and capabilities

Search results help identify an appropriate service before querying it. Schema inspection can reveal field names and data types before constructing a request, reducing guesswork when writing filters or selecting output fields. Layer queries support pagination with `limit` and `offset`, sorting with `order_by`, and retrieval of geometry alongside attributes.

The Arcgis Castateparks MCP server is suitable for agents that need to locate California State Parks layers, examine their structure, and extract records for downstream analysis or answers.

## Limitations and notes

The integration depends on the availability and contents of the California State Parks ArcGIS services. It does not describe datasets beyond the information returned by those services. Query arguments must use the target layer's actual field names and supported capabilities.

The gateway and standalone modes differ in scope: the gateway adds shared Pipeworx meta-tools, while the local stdio package lists only the three pack tools. The package is licensed under MIT.

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