Arcgis Longview

What Arcgis Longview MCP server does

The Arcgis Longview MCP server gives MCP clients access to City of Longview, Texas open geospatial datasets published through ArcGIS. Its dataset coverage includes areas such as parcels, zoning, public works, and city services, subject to what the city’s available data exposes.

The server has three pack-specific tools. search_datasets finds datasets by keyword and returns identifying information, a summary, record count, owner or organization, and a Feature Service URL. query_layer retrieves records from an ArcGIS Feature Service or Map Service layer. layer_info describes a layer’s schema and metadata before you query it.

How it works

A typical workflow starts with search_datasets. Use the returned service URL with layer_info to inspect field names, field types, geometry type, total records, and supported capabilities. Then pass the same URL to query_layer to retrieve matching records.

Queries support a SQL-like where expression, comma-separated out_fields, order_by, limit, and offset. To inspect a sample without adding a filter, use where="1=1" and out_fields="*". Query results contain attribute rows and geometry.

The Arcgis Longview MCP server can be reached through the Pipeworx gateway at its pack-specific MCP endpoint or through the full gateway. The pack endpoint lists its three tools along with shared Pipeworx meta-tools. The gateway also provides ask_pipeworx, which can route natural-language questions across the wider catalog.

Setup and configuration

For a remote connection, add the gateway URL to an MCP client configuration:

{
  "mcpServers": {
    "arcgis-longview": {
      "url": "https://gateway.pipeworx.io/arcgis-longview/mcp"
    }
  }
}

The package also runs locally over stdio with no Pipeworx account or gateway round-trip. Configure the client to run npx -y @pipeworx/mcp-arcgis-longview, or execute that command directly to verify that the process starts. The local process exposes only this pack’s tools, unlike the gateway connection, which includes shared meta-tools.

HTTP callers can invoke tools through the gateway’s REST endpoint. For example, a POST request to /v1/tools/arcgis_longview_search_datasets with a JSON query can search for datasets.

Tools and capabilities

• search_datasets: Find Longview GIS datasets by keyword and return service URLs and dataset metadata.
• query_layer: Retrieve ArcGIS layer records with filters, selected fields, sorting, pagination, and geometry.
• layer_info: Inspect layer fields, geometry type, record count, and capabilities.
• ask_pipeworx: Ask the gateway to select and parameterize an appropriate tool across its catalog.

Limitations and notes

The Arcgis Longview MCP server is focused on City of Longview GIS data; it is not described as a general ArcGIS search service. query_layer and layer_info require a layer URL, normally obtained from search_datasets.

Gateway and local connections expose different tool lists. A pack endpoint includes shared gateway meta-tools, while the standalone package exposes only the three Arcgis Longview tools. The gateway documentation states that its exact scope can change and that the initialize response is authoritative. The project is licensed under MIT.