NYC Open Data Capital Projects MCP Server
Related Servers
Alternatives to NYC Open Data Capital Projects MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to query live construction project data such as RFIs, submittals, budget variance, daily logs, punch lists, and inspection checklists.-

Akil MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to query NYC public records through a hosted MCP server, supporting civic workflows such as property research, business evaluation, public money tracking, and influence mapping.14 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query normalized US government data from SAM.gov, USAspending, Grants.gov, US House STOCK Act trades, and SEC EDGAR through 19 read-only tools covering contracts, awards, grants, congressional trades, insider filings, holdings, and financial fundamentals.1MIT No Attribution
- FlicenseNot gradedqualityDmaintenanceProvides 19 tools for discovery, data analysis, configuration, and simulation, enabling an agent to drive digital twin workflows with session persistence and knowledge graph capabilities.1-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude, Copilot and IDE agents to interrogate a building's digital twin in plain language through seven tools covering building overview, room lists, per-room design promises, diagnosed findings, room time series, sandboxed read-only SQL and BCF issue export. Answers whether each room still meets its own design intent — and why not — instead of relying on fixed thresholds.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to access and analyze financial data, stock information, company fundamentals, market insights, and 250+ tools across asset classes. Supports flexible hosted or self-hosted deployment with dynamic toolset management.332 npmApache 2.0
TDQS
Scored across 18 tools
Tools are cleanly split by domain (schedule vs budget) and by function (detail, history, breakdown, change, duration), so most purposes are distinct. There is mild overlap between rank_projects and project_portfolio (both listing/filtering entities) and between the breakdown/rank tools for aggregate cuts, but the descriptions disambiguate these well enough.
Names are consistently snake_case throughout. The only deviation is stylistic: some use verb_noun (get_project_schedule, list_agencies, resolve_project_reference, rank_projects) while others are noun-based (schedule_breakdown, dataset_info, project_portfolio), but this remains predictable and readable.
18 tools is slightly heavy but justified for a rich analytical domain spanning schedule and budget lenses with detail, history, change, duration, and aggregate operations. Each tool appears to earn its place, with run_sql serving as the general escape hatch.
The surface covers the full read-only analytical lifecycle: resolution, entity detail, per-period history, breakdowns, period-over-period changes, duration statistics, portfolio listing, rankings, dictionaries, schema/field introspection, and an arbitrary SQL fallback. No obvious gaps for a read-only open-data server.