Log inSubmit server
Data Pa logo

Data Pa

Query Pennsylvania Open Data catalog records and run Socrata SoQL queries through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Data Pa

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": {
    "data-pa": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-data-pa"
      ]
    }
  }
}

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

Automated check passed— started and listed 3 tools correctly (5d ago).

Overview

Data Pa MCP server connects AI agents to Pennsylvania's data.pa.gov Socrata open-data catalog. It provides tools to find datasets, inspect schemas and metadata, and run SoQL queries with filtering, grouping, sorting, pagination, and field selection. Use it when an agent needs structured Pennsylvania public data rather than general web search. It is available through the Pipeworx gateway or as a local stdio package.

Use cases

  • Search Pennsylvania datasets by topic
  • Inspect a dataset schema before querying
  • Run filtered SoQL queries against public records
  • Retrieve grouped or paginated dataset results

Key features

  • Pennsylvania Open Data catalog search
  • Socrata SoQL query execution
  • Dataset schema and metadata lookup
  • Filtering, grouping, ordering, and pagination
  • Hosted gateway and local stdio access

Tools3

What Data Pa lets your agent do. Expand a tool for its parameters.

Verified live~411 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.

7/7 checks healthy over the last 47d

What it can do

From the 3 tools this server returned when we ran it.

Read-only tools · 3
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age115 days
Maintainers1

Observed 2026-10-19 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · @pipeworx/mcp-data-pa (npm)

Adoption & maintenance

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

npm downloads442Package downloads in the last 30 days.
Last commit28d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed3Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Data Pa works

What the Data Pa MCP server does

The Data Pa MCP server gives an MCP client access to datasets published in Pennsylvania's Open Data catalog at data.pa.gov. It supports a discovery-to-query workflow: search the catalog, identify a dataset resource ID, inspect its structure, and then retrieve matching records.

Search results include each dataset's resource ID, name, description, category, and update date. The resource ID is the identifier used by the other tools. Metadata requests provide the dataset schema, column types, row count, category, and last-updated information, which helps an agent construct queries against unfamiliar datasets.

How it works

The Data Pa MCP server exposes three pack-specific tools: datasets, metadata, and query. The datasets tool searches the catalog by keyword. The metadata tool examines a selected resource, while query sends a Socrata SoQL request to that resource and returns matching rows as JSON.

Queries can include where, select, group, and order clauses, along with limit and offset values. The SoQL clause arguments do not include the leading $. A typical workflow is to search for a subject such as budgets, use the returned resource ID to inspect columns, and then write a query using the confirmed field names.

The hosted endpoint is https://gateway.pipeworx.io/data-pa/mcp. It is a scoped Pipeworx connection, so its tool list also includes shared gateway meta-tools. The gateway can route broader questions through ask_pipeworx, and the full gateway is available at https://gateway.pipeworx.io/mcp when direct access to all packs is preferred.

Setup and configuration

Add the hosted endpoint to an MCP client as a server URL. The README specifically lists Claude Desktop, Cursor, and Windsurf as compatible clients. No account is required for the first hosted calls according to the project documentation.

For a local connection, run the package with npx -y @pipeworx/mcp-data-pa and configure the client to start that command. This standalone mode communicates over standard input and output, does not require a Pipeworx account, and exposes only the three Data Pa tools rather than the gateway's shared meta-tools.

The tools can also be called over HTTP. For example, the hosted REST-style endpoint for dataset search is POST https://gateway.pipeworx.io/v1/tools/data_pa_datasets with a JSON body such as {"query":"budget"} and a Content-Type: application/json header.

Tools and capabilities

  • datasets: Search Pennsylvania's open-data catalog by keyword and return resource IDs plus basic dataset details.
  • metadata: Retrieve columns, types, row count, category, and last-updated information for a resource ID.
  • query: Run a SoQL query with selection, filtering, grouping, ordering, limits, and offsets, returning rows as JSON.
  • Hosted gateway access: Use shared Pipeworx tools, including ask_pipeworx, in addition to the pack-specific tools.

Limitations and notes

The local package and hosted pack endpoint expose the same Data Pa source tools, but they do not expose the same surrounding tool set. The hosted endpoint includes shared Pipeworx meta-tools, while the local stdio process does not. The gateway's initialize response is the authoritative source for the exact hosted tool scope at a given time.

Queries depend on the dataset's current schema and resource ID. Use metadata before writing a complex query when column names or types are unknown. The documented license is MIT.

Read the full README View source on GitHub

Reviews

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

Frequently Asked Questions about Data Pa

Data Pa is an MCP server that connects AI clients to Pennsylvania's data.pa.gov Socrata open-data catalog. Its main tools search datasets, retrieve dataset metadata and schemas, and run SoQL queries against selected resources, returning matching records as JSON.

Install it locally by configuring your MCP client to run `npx -y @pipeworx/mcp-data-pa`. This starts the standalone stdio server without a Pipeworx account. You can instead configure the hosted endpoint at `https://gateway.pipeworx.io/data-pa/mcp`.

Search for a dataset with `datasets`, inspect its resource with `metadata`, then call `query` using the resource ID. The query tool accepts SoQL `where`, `select`, `group`, and `order` clauses plus `limit` and `offset`.

Yes, Data Pa works with Cursor through the hosted MCP endpoint or its local stdio configuration. Add `https://gateway.pipeworx.io/data-pa/mcp` as the server URL, or configure Cursor to launch `npx -y @pipeworx/mcp-data-pa`.

Related MCP servers

All in Data Platforms All alternatives
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 PreviewData Pa AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/data-pa?style=directory)](https://allmcps.com/mcp/data-pa)
HTML Embed
<a href="https://allmcps.com/mcp/data-pa"><img src="https://allmcps.com/api/badge/data-pa?style=directory" alt="Data Pa on AllMCPs" /></a>