Data Norfolk logo

Data Norfolk

Searches Norfolk Open Data and runs SoQL queries against Socrata datasets through MCP.

Install Data Norfolk

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

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

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

Overview

The Data Norfolk MCP server connects AI agents to the Norfolk Open Data catalog at data.norfolk.gov. It provides tools to find datasets, inspect schemas and metadata, and run Socrata SoQL queries with filtering, grouping, sorting, pagination, and field selection. Use it when an agent needs current Norfolk public data identified by dataset resource ID. It is available through the Pipeworx gateway or as a local stdio package.

Use cases

  • Search Norfolk public datasets by topic
  • Inspect dataset columns and row counts
  • Run filtered SoQL queries against Norfolk data
  • Aggregate and paginate dataset results

Key features

  • Keyword search across Norfolk Open Data
  • Dataset schema and metadata lookup
  • SoQL filtering, selection, grouping, and ordering
  • JSON query results
  • Hosted gateway and local stdio modes

Tools3

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

Verified live~408 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 age113 days
Maintainers1

Observed 2026-10-17 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-norfolk (npm)

Adoption & maintenance

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

npm downloads443Package 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 activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Data Norfolk works

What Data Norfolk MCP server does

The Data Norfolk MCP server gives MCP clients access to Norfolk Open Data, a Socrata-powered catalog at data.norfolk.gov. It supports a workflow of finding a relevant dataset, checking its structure, and then retrieving matching records. Dataset results include the resource ID, name, description, category, and update date, so an agent can use the resource ID in subsequent calls.

The Data Norfolk MCP server is intended for questions that depend on public datasets published by Norfolk. It does not present a general database interface; requests target datasets in the Norfolk Open Data catalog and use Socrata’s query model.

Tools and capabilities

The server exposes three pack-specific tools:

  • datasets searches the catalog by keyword and returns dataset identification and descriptive fields, including the resource ID and last update date.
  • metadata retrieves a dataset’s schema and related information by resource ID. Results can include columns, data types, row count, category, and last-updated information.
  • query runs a SoQL request against a dataset by resource ID and returns matching rows as JSON. It accepts where, select, group, and order clauses without the leading $, along with limit and offset values.

A typical agent flow is to call datasets first, pass the selected resource ID to metadata when the column structure needs confirmation, and then use query to retrieve or aggregate records.

How it works

The hosted option uses the Pipeworx gateway. The pack endpoint is https://gateway.pipeworx.io/data-norfolk/mcp, while the full gateway is available at https://gateway.pipeworx.io/mcp. The pack endpoint lists the Norfolk tools together with shared Pipeworx meta-tools, so its tool list is larger than the three pack-specific tools. The exact scope is reported by the MCP initialize response.

Shared gateway tools can route broader questions through ask_pipeworx, including questions outside the directly listed Norfolk tools. Both hosted URLs use the same gateway and data-source network; they differ in which pack’s tools are listed directly.

The server can also be called over HTTP without an MCP client. Tool requests use the gateway’s /v1/tools/ endpoints, such as the endpoint for data_norfolk_datasets.

Setup and configuration

For a hosted MCP connection, add the pack endpoint to a client configuration under the data-norfolk server name. The README specifically shows Claude Desktop, Cursor, and Windsurf as compatible client examples.

For local use, run @pipeworx/mcp-data-norfolk with npx -y, or configure the package as a stdio MCP command. The local process communicates over standard input and output and exposes only the three Norfolk pack tools, without the gateway’s shared meta-tools or gateway routing. This standalone mode does not require a Pipeworx account or a gateway round trip.

Limitations and notes

Queries require a Norfolk Open Data resource ID, such as cab7-wvn5; use the catalog search tool to discover one when it is unknown. SoQL clauses must be supplied without their leading dollar sign. The hosted pack endpoint always includes shared gateway tools, while the local package does not. The gateway’s listed tool scope can change, so the initialize response is the authoritative source for a particular connection.

Reviews

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

Frequently Asked Questions about Data Norfolk

Data Norfolk is an MCP server that connects AI agents to the Norfolk Open Data Socrata catalog at data.norfolk.gov. Its main tools search datasets, retrieve schema and metadata, and run SoQL queries by resource ID, returning catalog details, dataset information, or matching rows as JSON.

Run `npx -y @pipeworx/mcp-data-norfolk` or configure that command as a local stdio MCP server. This mode requires no Pipeworx account and exposes the pack’s three tools. You can alternatively add the hosted MCP URL to a compatible client.

First use `datasets` to find a resource ID, then call `query` with that ID and any supported SoQL clauses. The tool accepts `where`, `select`, `group`, and `order` without `$`, plus `limit` and `offset`, and returns matching rows as JSON.

Yes, Cursor is shown as a supported client example in the README. Configure the hosted endpoint at `https://gateway.pipeworx.io/data-norfolk/mcp`, or use the local stdio command with `npx -y @pipeworx/mcp-data-norfolk`.

Related MCP servers

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