# NYC Traffic & Street Conditions AI Agent Connect > NYC Traffic & Street Conditions MCP provides direct access to Department of Transportation datasets without needing an API key. Your agent can pull specific motor-vehicle crash reports, track pothole repair progress, monitor pedestrian and bike volumes from city sensors, and map out the protected bike network. ## Overview - **Category:** government-public-data - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_iZp5oUFU0SfRxe8rVjSXOxN03igtngcDMCs3KHpg/ai-agent-connect - **Tags:** new-york, nyc, traffic, crashes, potholes, bicycles, bikes, sensors ## Description You can pull live street-level reality from the NYC Department of Transportation without managing complex API credentials. This MCP connects your AI client to official city datasets, turning raw government records into actionable intelligence. If you need to investigate safety trends, you can look up specific collision details or identify the most frequent contributing factors in recent crashes. For infrastructure tracking, you can query pothole work orders to see when specific repairs were completed or check the volume of bike and pedestrian traffic through the city's sensor network. It's a direct line to the data used by urban planners and journalists to understand how New York City moves and where the streets are failing. ## Tools ### get_bike_ped_sensor This tool provides the location, coverage, and data range for a specific bike or pedestrian count sensor. ### get_crash_injuries Use this to get full details on every person involved in a specific collision using a collision ID. ### get_pothole_work_order This tool retrieves all street segments associated with a specific pothole work order via its defnum. ### list_bike_routes Access the city's protected and signed bike network segments, filtered by borough, street, or facility class. ### search_bike_ped_counts This tool pulls hourly or interval volumes for bike and pedestrian traffic from the NYC sensor network. ### search_pothole_work_orders Search through closed DOT pothole work orders to track street condition repairs. ### search_traffic_crashes This tool searches NYC motor-vehicle crash reports using filters like borough, zip code, or date. ### top_crash_factors Identify the most frequent primary contributing factors for crashes within a specific time window. ## Prompt Examples **Prompt:** ``` What are the main causes of crashes in NYC over the last 365 days? ``` **Response:** ``` The top contributing factors for the last 365 days are [factor 1], [factor 2], and [factor 3]. ``` **Prompt:** ``` How much bike traffic was recorded on 6th Ave in Midtown recently? ``` **Response:** ``` Based on sensor data for the 6th Ave corridor, the interval volumes for bikes are [count] per hour. ``` **Prompt:** ``` When was the pothole repair on 14th St finished? ``` **Response:** ``` The work order for that segment was closed on [date]. ``` ## Capabilities ### Crash Investigation Your agent can pull specific injury details and contributing factors for any recorded collision. ### Infrastructure Monitoring The AI can track the status and completion dates of pothole repair work orders. ### Mobility Analysis Your client can query sensor networks to get precise bike and pedestrian counts. ### Route Mapping The agent can identify segments of the city's protected bike lane network. ## Use Cases ### Safety Audits An analyst uses the crash factor tools to identify dangerous intersections for new bike lane proposals. ### Maintenance Tracking A researcher checks the completion dates of pothole repairs to evaluate city response times. ### Traffic Volume Studies A planner uses sensor counts to determine if a specific street needs more pedestrian infrastructure. ### News Reporting A journalist pulls recent crash data to write stories about street safety trends in specific boroughs. ## Benefits - Access DOT datasets without managing your own API keys. - Query granular person-level injury data from specific crashes. - Track street maintenance through closed pothole work orders. - Get real-time sensor volumes for pedestrians and cyclists. ## How It Works Connecting to this data is a single-step process that gives your AI client immediate access to NYC's open data. 1. Connect your preferred MCP-compatible client to Vinkius. 2. Select the NYC Traffic & Street Conditions MCP from the catalog. 3. Ask your AI client to search for specific crashes, sensors, or work orders. 4. The AI executes the tool and presents the raw city data in a readable format. ## Frequently Asked Questions **Do I need an NYC Open Data API key?** No. This MCP handles the connection to the DOT datasets so you don't have to manage keys. **Can I see specific injury details for a crash?** Yes. If you have a collision ID, you can use the tool to see the age, injury severity, and safety equipment used by people in that crash. **How can I find out if a pothole has been fixed?** You can search for closed pothole work orders using the street name or a specific work order number. **What kind of sensor data is available?** The MCP provides interval volumes for both bike and pedestrian traffic from the city's sensor network. **Which AI clients can I use with this MCP?** You can use this with any MCP-compatible client like Claude, Cursor, Windsurf, or VS Code. **Do I need an API key?** 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. **How current is the data?** Each dataset is updated on its own cadence (311 daily, trip records yearly, tonnage monthly, ...). The get tools and search_datasets expose the last update timestamp, and the rows you read are the platform's current state. **What do the crash injury numbers mean?** Each crash row carries the counts of persons/pedestrians/cyclists/motorists injured and killed, plus the recorded contributing factors for up to five vehicles. The per-person detail (severity, age, equipment) is a separate dataset, joined by collision_id.