# Data Piercecounty [Health: Active]

**Category:** 📊 Data Platforms  
**Repository:** https://github.com/pipeworx-io/mcp-data-piercecounty  
**GitHub Stars:** 0  
**npm Downloads (last month):** 434  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/data-piercecounty

## Description
Pierce County Open Data (internal.open.piercecountywa.gov) Socrata MCP.

## Tools
Capabilities this server exposes over MCP:

- **datasets** — Search the Pierce County Open Data catalog of open datasets by keyword. Returns each dataset's resource_id, name, description, category and update date — pass the resource_id to query/metadata.
- **query** — Run a Socrata SoQL query against a Pierce County Open Data dataset by resource_id (e.g. "hmbh-c3hw"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.
- **metadata** — Get a Pierce County Open Data dataset's schema + metadata (columns, types, row count, category, last-updated) by resource_id, e.g. "hmbh-c3hw".

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "data-piercecounty": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-data-piercecounty"]
  }
}
```

## Documentation

## What Data Piercecounty does

Data Piercecounty exposes the Pierce County Open Data catalog at `internal.open.piercecountywa.gov` through three MCP tools. It is intended for agents that need to discover county datasets, understand their structure, and retrieve selected records without manually navigating the catalog.

The workflow starts with `datasets`, which searches catalog entries by keyword. Results include each dataset’s resource ID, name, description, category, and update date. The returned resource ID is then used with the other tools. For example, a result such as `hmbh-c3hw` identifies the dataset to inspect or query.

## Tools and capabilities

- `datasets`: Searches the Pierce County catalog by keyword and returns dataset identification and catalog details.
- `metadata`: Retrieves a dataset’s schema and descriptive information, including columns, data types, row count, category, and last-updated time.
- `query`: Executes a Socrata SoQL query against a selected dataset and returns matching rows as JSON.

`query` accepts `where`, `select`, `group`, and `order` expressions, along with `limit` and `offset`. The SoQL expressions should be supplied without the leading `$` used in some HTTP API examples. This supports narrowing results, choosing fields, grouping records, ordering output, and paginating through rows.

## How it works

The hosted configuration connects an MCP client to `https://gateway.pipeworx.io/data-piercecounty/mcp`. That endpoint exposes the Pierce County tools and also includes shared Pipeworx gateway tools, such as `ask_pipeworx`, `discover_tools`, `search_within`, and memory-related tools. The exact tool list is returned during MCP initialization and can be larger than the three Pierce County-specific tools.

The same gateway can be reached at `https://gateway.pipeworx.io/mcp`, which lists all packs directly. The scoped endpoint and full gateway access the same broader Pipeworx source collection; the difference is which pack appears directly in the tool list. `ask_pipeworx` can route questions across that collection from either gateway URL.

A local alternative runs only the Pierce County package over stdin and stdout. It uses the same source and core tools without gateway routing or the shared meta-tools. The gateway also exposes HTTP tool calls, including a POST endpoint for invoking `datasets`, which can be useful when an MCP client is not available.

## Setup and configuration

Add the hosted endpoint to an MCP client such as Claude Desktop, Cursor, or Windsurf:

```json
{
  "mcpServers": {
    "data-piercecounty": {
      "url": "https://gateway.pipeworx.io/data-piercecounty/mcp"
    }
  }
}
```

For a local stdio connection, configure the package through `npx`:

```json
{
  "mcpServers": {
    "data-piercecounty": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-data-piercecounty"]
    }
  }
}
```

The package can also be started directly with `npx -y @pipeworx/mcp-data-piercecounty`. Initial gateway calls do not require an account. Local execution avoids the gateway and its network round trip.

## Limitations and notes

This is an independent, unofficial integration rather than a Pierce County government service. Queries depend on the datasets and fields available in the Pierce County Open Data catalog. Gateway connections include additional shared tools, while the standalone package exposes only the three pack-specific tools. The full gateway and the scoped endpoint both provide access to the wider Pipeworx collection through routing, but only the relevant pack is listed directly by the scoped endpoint.

_Full upstream README: https://allmcps.com/mcp/data-piercecounty/readme_

