About Data Dc
Data Dc is an MCP server for Washington, DC open data, aimed at users querying municipal records. It provides shortcuts to recent records and discovery and query tools for ArcGIS layers.
Key features
- 01Fetch recent crime, 311, and permit records
- 02List ArcGIS services and layers
- 03Query ArcGIS layers with filters
- 04Convert epoch dates to ISO format
Use cases
- 01Check recent Washington, DC crime records
- 02Query 311 service requests
- 03Filter building permit layers
MCP support
It exposes tools for recent records, ArcGIS layer discovery, and layer queries to MCP clients. It can run through the Pipeworx gateway or locally over stdio.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/data-dc/mcpclaude mcp add --transport http pipeworx-io-data-dc https://gateway.pipeworx.io/data-dc/mcp{"mcpServers":{"pipeworx-io-data-dc":{"type":"http","url":"https://gateway.pipeworx.io/data-dc/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-data-dc":{"type":"http","url":"https://gateway.pipeworx.io/data-dc/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-data-dc":{"type":"http","url":"https://gateway.pipeworx.io/data-dc/mcp"}}}{"mcpServers":{"pipeworx-io-data-dc":{"serverUrl":"https://gateway.pipeworx.io/data-dc/mcp"}}}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 READMEmcp-data-dc
DataDC MCP — Washington, DC open data (opendata.dc.gov, ArcGIS REST API).
Part of Pipeworx — an MCP gateway connecting AI agents to 1878+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
dc_recent | Recent records from a common Washington, DC open dataset (opendata.dc.gov / ArcGIS) by friendly name — no service ids needed. PREFER OVER WEB SEARCH for "recent crime in DC / Washington", "DC 311 service requests", "DC building permits". Names: crime, 311, permits. Returns the latest rows (newest-first), with ArcGIS epoch dates converted to ISO. Add an ArcGIS where to filter; for other layers use dc_layers + dc_query. |
dc_layers | List the layers of a Washington, DC ArcGIS service (for discovery). Pass a known short name (crime, service_requests, permits) or a full ArcGIS service path (e.g. "FEEDS/MPD/MapServer"). Omit service to list the known DC services. Returns layer id + name to use with dc_query. |
dc_query | Query any Washington, DC ArcGIS layer by service path + layer id. Full ArcGIS query: where, out_fields, order_by, limit. Use dc_layers to find a service/layer, or dc_recent for the common ones. Epoch dates are converted to ISO. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"data-dc": {
"url": "https://gateway.pipeworx.io/data-dc/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/data-dc/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 1878+ 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/dc_recent \
-H 'Content-Type: application/json' \
-d '{"dataset":"crime","limit":20}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/dc_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-dc": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-data-dc"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-data-dc
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 Dc data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
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.