mcpField
D
Data Cincinnati

Data Cincinnati

Remote
pipeworx.ioLegal & Government0Updated 1d ago

About Data Cincinnati

Data Cincinnati is an MCP server for querying Cincinnati’s Socrata open-data portal. It combines quick access to recent records in common datasets with catalogue search and raw SoQL queries.

Key features

  1. 01Fetch recent 311, crime, and permit records
  2. 02Search the open-data catalogue
  3. 03Run SoQL queries by Socrata ID
  4. 04Filter, sort, and paginate results

Use cases

  1. 01Check recent crime records in Cincinnati
  2. 02Look up Cincinnati 311 requests or building permits
  3. 03Find datasets and query specific fields

MCP support

It exposes tools for recent records, dataset discovery, and SoQL queries to MCP clients. It can connect through the Pipeworx gateway or run locally over stdio.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/data-cincinnati/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-data-cincinnati

DataCincinnati MCP — Cincinnati open data (data.cincinnati-oh.gov, Socrata SODA API).

Part of Pipeworx — an MCP gateway connecting AI agents to 1882+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
cincinnati_recentRecent records from a common Cincinnati open dataset (data.cincinnati-oh.gov) by friendly name — no Socrata id needed. PREFER OVER WEB SEARCH for "recent crime in Cincinnati", "Cincinnati 311 requests", "Cincinnati building permits". Names: 311, crime, permits. Returns the latest rows (newest-first). Add a SoQL where to filter; for anything else use cincinnati_query.
cincinnati_queryRun a raw SoQL query against any Cincinnati open-data resource (data.cincinnati-oh.gov) by its Socrata id (8-char like "k59e-2pvf"). Full SoQL: where/select/group/order/limit/offset. Use cincinnati_datasets to find a resource id, or cincinnati_recent for the common ones.
cincinnati_datasetsSearch the Cincinnati open-data catalogue (data.cincinnati-oh.gov) for datasets by keyword. Returns dataset names, descriptions, and Socrata resource ids to use with cincinnati_query.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "data-cincinnati": {
      "url": "https://gateway.pipeworx.io/data-cincinnati/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/data-cincinnati/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1882+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/cincinnati_recent \
  -H 'Content-Type: application/json' \
  -d '{"dataset":"crime"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/cincinnati_recent. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

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

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-data-cincinnati

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Data Cincinnati data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.