NYC Open Data Capital Projects MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NYC Open Data Capital Projects MCP ServerShow me the capital projects with largest schedule delays"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
NYC Open Data — Capital Projects MCP Server
A local MCP server over the NYC Capital Projects Dashboard (CPD) datasets on NYC Open Data. It ingests four public Socrata datasets into a single local DuckDB and exposes 16 tools so an AI assistant can answer schedule, budget, and lifecycle questions about NYC capital projects — with the domain rules (PID↔FMS many-to-many, role-aware agency attribution, signed variance reporting) baked into the tools instead of left for the caller to rediscover.
Source datasets (Socrata)
ID | Dataset |
| Citywide Capital Project List Detail (the schedule↔budget edge) |
| Citywide Budget & Spend by FY |
| Citywide Budget Spend History & Variance |
| Citywide Schedule History & Variance |
Related MCP server: Project Guardian MCP
Quickstart
Requires Python ≥ 3.12 and uv.
uv sync
uv run od-cpd init # download + materialize all 4 datasets → ./var/cpd.duckdb
uv run od-cpd status # per-dataset freshness vs Socrata
uv run od-cpd update # re-ingest when Socrata publishes a new periodOptional: set OD_CPD_SOCRATA_APP_TOKEN to a free
Socrata app token to avoid
anonymous rate limits during ingest.
Connect an MCP client
The server speaks stdio. With Claude Code:
claude mcp add od-cpd --env PYTHONPATH=/path/to/repo/src -- \
uv run --directory /path/to/repo od-cpd-serverOr in any client's JSON config:
{
"mcpServers": {
"od-cpd": {
"command": "uv",
"args": ["run", "--directory", "/path/to/repo", "od-cpd-server"],
"env": { "PYTHONPATH": "/path/to/repo/src" }
}
}
}(PYTHONPATH makes the launch robust when uv's editable install is flaky —
e.g. on iCloud-synced paths.)
What's inside
docs/FEATURES.md— the canonical inventory: all 16 tools and every domain rule the server encodes. Start here.
The headline domain rules, briefly:
"Project" is ambiguous. A PID identifies a schedule; an FMS ID identifies a budget line. They are many-to-many (~3% fan out), so the tools list all counterparts rather than silently picking one.
Agency attribution is role-aware. "Agency X's projects" means the sponsor (owner) view for normal agencies, but the managing (builder) view for the three construction-manager agencies (DDC/DCAS/EDC).
Values are reported signed and neutral ("moved 45 days later", "budget grew $2.1M") rather than only surfacing one direction.
Layout
src/od_cpd/— ingest, materialization, and the MCP server + toolsdata/— curated agency/category dictionaries (YAML, tracked)tests/— unit tests + golden evals (uv run pytest)var/,exports/— runtime DuckDB + exports (gitignored, regenerable)
Develop
uv run pytest # fallback: PYTHONPATH=src python -m pytestClassification is dictionary-driven: edit data/agencies.yaml /
data/categories.yaml (not Python) to adjust agency or category mappings,
then re-materialize. See CLAUDE.md for the atomic-swap pattern that applies
materialization changes without re-downloading.
Data caveats
This is an independent project, not affiliated with the City of New York.
Figures reflect whatever reporting period the underlying Socrata datasets
carry at ingest time; always check dataset_info for the current period and
per-dataset caveats.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/WillHsiaoNYC/NYC-Opendata-Capital-Projects-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server