Data Nashville logo

Data Nashville

Query Nashville open data through ArcGIS layers, including recent crime, 311 requests, permits, and custom filtered records.

Install Data Nashville

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

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

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Data Nashville MCP server exposes Nashville open data from data.nashville.gov and ArcGIS REST services through three tools. Use nashville_recent for common crime and 311 datasets, nashville_layers to discover services and layer IDs, and nashville_query for full ArcGIS queries. It is available as a hosted MCP endpoint or an npm-based stdio bridge that forwards requests to the Pipeworx gateway. Reach for it when an agent needs structured Nashville records rather than web search results.

Use cases

  • Retrieve recent Nashville crime records
  • Filter Nashville 311 service requests
  • Discover ArcGIS services and layer IDs
  • Query Nashville permits or other ArcGIS layers
  • Convert Nashville date fields into ISO values

Key features

  • Recent crime and 311 dataset retrieval
  • Nashville ArcGIS layer discovery
  • Filtered queries across ArcGIS layers
  • Newest-first record ordering
  • Epoch date conversion to ISO format
  • Hosted MCP and local stdio access

Tools3

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

Self-reported~221 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 2d ago

Recent health check succeeded.

11/11 checks healthy over the last 62d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

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

Adoption & maintenance

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

npm downloads449Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Data Nashville works

What Data Nashville MCP server does

Data Nashville provides MCP access to Nashville public datasets backed by data.nashville.gov and ArcGIS REST services. Its main use is retrieving structured records such as recent crime data and Nashville 311 service requests, while also supporting broader exploration of available ArcGIS services and layers.

The integration is unofficial and independent of the upstream data provider. Results can be used directly by MCP-compatible clients or through the gateway's HTTP tool interface.

How it works

The hosted endpoint is available at https://gateway.pipeworx.io/data-nashville/mcp. An MCP client can connect to that URL and invoke the Nashville-specific tools. The endpoint also exposes shared Pipeworx gateway tools, including routing and discovery functions, so its complete tool list is broader than the three Nashville tools.

A local npm package, @pipeworx/mcp-data-nashville, provides a stdio bridge. The client starts the package with npx, and the bridge sends requests to the same hosted endpoint. It requires network access and has no offline mode.

Requests can also be sent over HTTP to the gateway's tool API. Anonymous use is available for initial calls, with a daily limit; a Pipeworx account and API key provide a higher daily allowance.

Setup and configuration

For a hosted MCP connection, add the endpoint to the client's MCP configuration:

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

For local stdio use, configure npx with the package name:

config.json
{
  "mcpServers": {
    "data-nashville": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-data-nashville"]
    }
  }
}

Set PIPEWORX_API_KEY in the stdio server environment to authenticate with a Pipeworx key. Anonymous calls are capped at 50 per day, while a free account raises the limit to 200 per day. Set PIPEWORX_META_TOOLS=1 if the local bridge should list shared gateway tools such as ask_pipeworx; otherwise, it lists the Nashville pack's tools by default.

Tools and capabilities

  • nashville_recent retrieves newest-first records from the common crime and 311 datasets. It accepts an ArcGIS where filter, and converts epoch date values to ISO-formatted dates.
  • nashville_layers lists layers for a known short service name, a full ArcGIS service path, or the known Nashville services when no service is supplied. Its layer IDs and names support follow-up queries.
  • nashville_query targets any Nashville ArcGIS layer by service path and layer ID. It supports ArcGIS query parameters including where, out_fields, order_by, and limit, and converts epoch dates to ISO format.

Limitations and notes

The stdio bridge depends on network connectivity to the Pipeworx gateway. The scoped hosted endpoint includes shared gateway meta-tools in addition to the Nashville tools, and the exact combined scope is returned during MCP initialization. Behind an HTTPS proxy, Node's built-in fetch may require NODE_USE_ENV_PROXY=1 on Node versions that support that setting.

Reviews

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

Frequently Asked Questions about Data Nashville

Data Nashville is an MCP server that connects AI clients to Nashville open data from data.nashville.gov and ArcGIS REST services. Its main tools retrieve recent crime and 311 records, discover service layers, and run filtered queries against Nashville ArcGIS layers with options for fields, ordering, limits, and date conversion.

Install it as a local stdio bridge by configuring your MCP client to run `npx -y @pipeworx/mcp-data-nashville`. The package forwards requests to the Pipeworx gateway and needs network access. You can also connect directly to the hosted MCP URL without installing a local package.

Yes, Data Nashville works with Claude Desktop, Cursor, and Windsurf through its hosted MCP endpoint or local stdio package. Add the gateway URL for a remote connection, or configure `npx -y @pipeworx/mcp-data-nashville` as the MCP server command.

Use `nashville_layers` to find a service and layer ID, then call `nashville_query` with the service path and layer ID. The query supports ArcGIS `where`, `out_fields`, `order_by`, and `limit` parameters. Use `nashville_recent` for the common crime and 311 datasets.

No, the npm bridge can make anonymous calls without an API key, subject to a 50-call daily limit. Set `PIPEWORX_API_KEY` to use a Pipeworx account and raise the daily allowance to 200 calls with a free account.

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