NYC Traffic & Street Conditions

NYC Traffic & Street Conditions MCP Connector for Claude

A+

Keyless NYC street data: DOT motor-vehicle crashes with per-person injuries, pothole work orders, bike & pedestrian sensor counts, sensors and the city's bike route network — no API key.

8 tools Official Updated Oct 1, 2026 Official Vinkius Partner

Street-surface reality from the Department of Transportation's open datasets, keyless.

What you can do

  • Search crashes — DOT motor-vehicle crash reports: date, borough, street, injuries/kills and the primary contributing factor
  • Crash person detail — every recorded person in one collision: type, injury severity, age, safety equipment
  • Pothole work orders — closed DOT pothole work orders by street or letter code, plus one order's full segments
  • Bike/ped counts — interval volumes from the city's sensor network, by sensor and travel mode
  • Sensor detail — location, coverage and data range of one count sensor
  • Bike routes — segments of the protected/signed bike network with facility class
  • Top crash factors — most frequent primary contributing factors in a trailing window

Who is this for

Urban planning, mobility analysis, road-maintenance tracking and newsroom data journalism on street safety.

new-yorknyctrafficcrashespotholesbicyclesbikessensors

8 tools expose this connector's capabilities to your AI agent.

get_bike_ped_sensor

Use the sensor_id from search_bike_ped_counts. Details of one bike/ped count sensor (location, coverage, data range)

get_crash_injuries

Give the collision_id from search_traffic_crashes. Person counts per crash are small, so results are complete. All persons (injuries) recorded in one crash, by collision id

get_pothole_work_order

A work order can span multiple street segments, so several rows may come back. One pothole work order (all segments) by its defnum

list_bike_routes

). Filter by boro, exact street or facility class. City protected/signed bike route segments with facility class

search_bike_ped_counts

sensor_id identifies the sensor (look it up with get_bike_ped_sensor); travelmode is "Bike" or "Pedestrian". timestamps are ISO; counts is the interval volume for that direction/flow. Hourly/interval bike & pedestrian counts from NYC sensor network

search_pothole_work_orders

boro is a single-letter code, not a name. defnum is the work-order number (starts with "DB"). Search closed DOT pothole work orders (street conditions)

search_traffic_crashes

Filter by borough, zip_code or a crash_date window ("YYYY-MM-DD"). For the per-person detail of one crash, use get_crash_injuries with the collision_id. Search NYC motor vehicle crashes (DOT) with injury counts

top_crash_factors

Widen or narrow with days. Counts cover all of the city; use search_traffic_crashes to drill into one borough or street. Most frequent primary contributing factors in crashes over a window

See how to talk to your AI agent using NYC Traffic & Street Conditions.

Most crash-prone areas in the last year

top_crash_factors with days=365 returns the leading contributing factors citywide; search_traffic_crashes with a borough filter then narrows to streets.

How busy is the bike lane on 6th Ave, Midtown?

search_bike_ped_counts with travelmode "Bike" and a sensor id covering that stretch (find it via the sensor dataset) returns interval volumes; list_bike_routes shows which segments carry protected lanes.

When was the pothole on 14th St fixed?

get_pothole_work_order with the work-order defnum returns every segment with rptdate and rptclosed — the close date shows when it was fixed.

No. NYC Open Data serves all public datasets anonymously over its SODA API (data.cityofnewyork.us). This MCP defines no credentials and needs nothing configured.

Related Connectors