# Arcgis Sanjose [Health: Active]

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

## Description
City of San Jose GIS — San Jose, California open geospatial data (ArcGIS).

## Tools
Capabilities this server exposes over MCP:

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

## Documentation

## What Arcgis Sanjose MCP server does

Arcgis Sanjose MCP server exposes selected City of San Jose GIS data through the Model Context Protocol. It is intended for applications that need to discover and inspect public geospatial datasets, then retrieve records from the relevant ArcGIS service. Supported dataset areas include parcels, zoning, public works, and city services.

The integration is an independent, unofficial connection and is not affiliated with, endorsed by, or published by the City of San Jose or its upstream provider. It belongs in the 🗺️ Location Services category for agents working with municipal geographic data.

## How it works

The normal workflow starts with `search_datasets`. Give the tool a keyword, and it returns matching dataset names, summaries, record counts, owners or organizations, and Feature Service URLs. Pass one of those URLs to `layer_info` to inspect the available fields, geometry type, record count, and service capabilities, or to `query_layer` to retrieve records.

`query_layer` accepts a SQL-like `where` expression, a comma-separated `out_fields` list, ordering, and limit and offset values. Results include attribute rows and geometry. For a basic sample, use a condition such as `1=1` and request all fields with `*`, where supported by the target service.

## Setup and configuration

The Arcgis Sanjose MCP server is available through the Pipeworx gateway at `https://gateway.pipeworx.io/arcgis-sanjose/mcp`. Add that URL to an MCP client as a remote server. The gateway endpoint also exposes shared Pipeworx meta-tools in addition to this pack’s three direct tools, so its tool list is larger than the pack-specific list.

A local alternative uses the npm package `@pipeworx/mcp-arcgis-sanjose` with an MCP client command configuration. Run it with `npx -y @pipeworx/mcp-arcgis-sanjose`; the process communicates over standard input and output and exposes only the pack’s own tools. The gateway and local package use the same source and tools.

The tools can also be called over HTTP without an MCP client. For example, the gateway exposes a POST endpoint for the dataset search tool under `/v1/tools/arcgis_sanjose_search_datasets`.

## Tools and capabilities

- `search_datasets`: Find San Jose GIS datasets by keyword and return metadata plus a service URL.
- `query_layer`: Retrieve filtered, selected, ordered, and paginated records from an ArcGIS Feature Service or Map Service layer.
- `layer_info`: Inspect layer fields, geometry type, record count, and capabilities before querying.

The gateway connection additionally lists shared tools such as `ask_pipeworx`, `discover_tools`, `search_within`, `remember`, and `recall`. These are gateway-wide tools rather than Arcgis Sanjose-specific data operations. `ask_pipeworx` can route questions across the broader Pipeworx catalog.

## Limitations and notes

The Arcgis Sanjose MCP server is limited to the City of San Jose GIS datasets exposed through the connected ArcGIS services. Results depend on the source layer and its supported capabilities. The gateway pack endpoint cannot currently be mounted without the shared gateway meta-tools; use the local stdio package when only the three ArcGIS tools are needed.

The gateway and local modes differ in transport and tool scope, not in the listed ArcGIS data operations. The gateway documentation states that its initialization response is authoritative for the exact tools available at a given time.

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