Arcgis Castateparks logo

Arcgis Castateparks

Search, inspect, and query California State Parks open GIS layers through ArcGIS MCP tools.

Install Arcgis Castateparks

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "arcgis-castateparks": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-arcgis-castateparks"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Arcgis Castateparks MCP server exposes California State Parks open geospatial data through ArcGIS dataset search and layer queries. Agents can find parks, trails, recreation, and natural-resource datasets, inspect schemas, then retrieve filtered records and geometry from Feature or Map Service layers. It can run locally over stdio or connect through the Pipeworx streamable HTTP gateway. Use it when an agent needs structured California State Parks GIS data rather than general web search.

Use cases

  • Find California State Parks trail datasets by keyword
  • Inspect ArcGIS layer fields before writing a query
  • Filter park or recreation records with SQL-like conditions
  • Retrieve paginated GIS attributes and geometry

Key features

  • Searches California State Parks GIS datasets
  • Inspects ArcGIS layer schemas and capabilities
  • Queries Feature Service and Map Service layers
  • Supports filters, field selection, sorting, and pagination
  • Returns attribute records and geometry
  • Runs through gateway HTTP or local stdio

Tools3

What Arcgis Castateparks lets your agent do. Expand a tool for its parameters.

Self-reported~169 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

9/9 checks healthy over the last 50d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @pipeworx/mcp-arcgis-castateparks (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads593Package downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.

How Arcgis Castateparks works

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Arcgis Castateparks

Arcgis Castateparks is an MCP server that connects AI agents to California State Parks open GIS data through ArcGIS Feature and Map Service layers. Its main tools search datasets, inspect layer schemas, and query records with filters, selected fields, sorting, pagination, and returned geometry.

Install it locally by running `npx -y @pipeworx/mcp-arcgis-castateparks` and configuring that command as a stdio MCP server. Alternatively, connect an MCP client to `https://gateway.pipeworx.io/arcgis-castateparks/mcp` through the Pipeworx gateway.

Yes, the README provides a Cursor configuration using the Pipeworx MCP endpoint. Add `https://gateway.pipeworx.io/arcgis-castateparks/mcp` as the server URL, or use the local npm package through stdio.

First call `search_datasets` with a keyword, then pass a returned Feature Service URL to `layer_info` or `query_layer`. Use `where`, `out_fields`, `order_by`, `limit`, and `offset` to control the query.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewArcgis Castateparks AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/arcgis-castateparks?style=directory)](https://allmcps.com/mcp/arcgis-castateparks)
HTML Embed
<a href="https://allmcps.com/mcp/arcgis-castateparks"><img src="https://allmcps.com/api/badge/arcgis-castateparks?style=directory" alt="Arcgis Castateparks on AllMCPs" /></a>