# Data Norfolk [Health: Active]

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

## Description
Norfolk Open Data (data.norfolk.gov) Socrata MCP.

## Tools
Capabilities this server exposes over MCP:

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

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

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

## Documentation

## What Data Norfolk does

Data Norfolk exposes Norfolk Open Data as MCP tools for dataset discovery and structured querying. The source is the Socrata-powered catalog at data.norfolk.gov. Agents can search the catalog by keyword, identify a dataset’s resource ID, inspect its structure, and retrieve matching records as JSON.

The integration is unofficial and independent of Norfolk’s upstream data provider. It is intended for working with publicly available catalog data through an MCP-compatible client or direct HTTP calls to the Pipeworx gateway.

## How it works

The typical workflow starts with `datasets`, which searches the Norfolk catalog and returns dataset identifiers, names, descriptions, categories, and update dates. Pass the returned `resource_id` to `metadata` to examine the dataset’s columns, data types, row count, category, and last-updated value.

Use `query` with a resource ID to run a Socrata SoQL request. The tool accepts `where`, `select`, `group`, and `order` expressions without the leading `$`, along with `limit` and `offset` for result control. Matching rows are returned as JSON.

## Setup and configuration

For a remote connection, add the Pipeworx endpoint to an MCP client:

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

Claude Desktop, Cursor, and Windsurf are shown as compatible client examples. The gateway endpoint includes the pack’s three tools plus shared Pipeworx meta-tools, including `ask_pipeworx`, `discover_tools`, `search_within`, and memory-related tools. The exact tool scope is reported during MCP initialization.

A local stdio installation is also available through the npm package:

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

Running `npx -y @pipeworx/mcp-data-norfolk` starts the server directly. The local process communicates over stdin and stdout and exposes only the Data Norfolk tools, without the gateway’s shared meta-tools.

## Tools and capabilities

- `datasets`: Find Norfolk Open Data datasets by keyword and return identifiers plus catalog details.
- `metadata`: Retrieve a dataset’s schema and descriptive information using its resource ID.
- `query`: Execute SoQL selections and filters, including grouping, ordering, limits, and offsets.
- HTTP access: Call gateway tools directly through endpoints such as `/v1/tools/data_norfolk_datasets`.
- Gateway routing: Use `ask_pipeworx` to submit a plain-language question that the gateway routes to an appropriate tool.

## Limitations and notes

The gateway and local package expose different tool lists even though they use the same Data Norfolk source tools. A pack-specific gateway connection also includes shared Pipeworx tools, while the standalone process does not. The gateway documentation states that initial calls require no account. Direct HTTP use requires POST requests with JSON bodies for tool calls, and tool inspection is available through the gateway’s HTTP API.

The integration is not affiliated with, endorsed by, or published by Norfolk’s upstream provider. Query operations depend on valid Socrata resource IDs and SoQL expressions for the selected dataset.

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