# Data Nj [Health: Active]

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

## Description
New Jersey Open Data (data.nj.gov) Socrata MCP.

## Tools
Capabilities this server exposes over MCP:

- **datasets** — Search the New Jersey 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 New Jersey Open Data dataset by resource_id (e.g. "44xg-bswk"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.
- **metadata** — Get a New Jersey Open Data dataset's schema + metadata (columns, types, row count, category, last-updated) by resource_id, e.g. "44xg-bswk".

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

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

## Documentation

## What Data Nj does

Data Nj gives MCP-compatible AI clients access to the New Jersey Open Data catalog at data.nj.gov. It works with Socrata datasets and exposes three pack-specific tools:

- `datasets` searches the catalog by keyword and returns each matching dataset’s resource ID, name, description, category, and update date.
- `metadata` retrieves a dataset’s schema and catalog details by resource ID, including columns, data types, row count, category, and last-updated information.
- `query` runs a Socrata SoQL query against a dataset identified by resource ID and returns matching rows as JSON.

A typical workflow starts with `datasets` to find a relevant resource ID, continues with `metadata` to understand its fields, and then uses `query` to retrieve the required records.

## How it works

The `query` tool accepts SoQL clauses through arguments for `where`, `select`, `group`, and `order`. These values use the clause syntax without the leading `$`. `limit` and `offset` support result-size control and pagination. Dataset identifiers such as `44xg-bswk` select the Socrata resource targeted by the request.

The remote MCP endpoint is available at `https://gateway.pipeworx.io/data-nj/mcp`. The same Pipeworx gateway also exposes shared gateway tools, including routing and discovery tools, in addition to the Data Nj tools. A local installation exposes only the three Data Nj tools.

Without an MCP client, the gateway can be called over HTTP. For example, `POST https://gateway.pipeworx.io/v1/tools/data_nj_datasets` with a JSON body such as `{"query":"crime"}` searches the catalog.

## Setup and configuration

For a remote connection, add the following MCP server entry to a compatible client:

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

The package also runs locally over standard input and output with no Pipeworx account or gateway round trip:

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

Run `npx -y @pipeworx/mcp-data-nj` directly to start the local server. It handles MCP `initialize`, `tools/list`, and `tools/call` requests over stdin and stdout.

## Tools and capabilities

### `datasets`

Searches New Jersey’s open-data catalog by keyword. Results provide the resource ID needed by the other tools, along with identifying and catalog information.

### `metadata`

Looks up a dataset’s structure and catalog metadata from its resource ID. Use it before querying when the available columns or their types are unknown.

### `query`

Executes a Socrata SoQL request for a resource ID. Field selection, filtering, grouping, ordering, limits, and offsets can be supplied through the tool arguments, with result rows returned as JSON.

## Limitations and notes

The gateway endpoint is an independent, unofficial integration and is not affiliated with, endorsed by, or published by the upstream New Jersey Open Data provider. The gateway’s scoped endpoint includes shared Pipeworx meta-tools alongside the pack tools; its exact listed scope is reported by the MCP `initialize` response. The standalone package does not include those shared tools or gateway-wide routing.

The first gateway calls do not require an account, and the standalone package operates without a Pipeworx account. Both connection styles access the Data Nj tool set, but only the gateway provides the broader Pipeworx routing behavior.

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