Connect Nyc Traffic Street Conditions to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Get real-time street data directly in your AI client.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

How Vinkius works: one connection, every tool, in any AI
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Complete set · 8 capabilities

The complete NYC Open Data capability set.

These are the exact actions your AI can choose when you ask it to work with NYC Open Data.

Capability set01 / 02

01-04

4 capabilities in this set.

Part of 8 available through NYC Open Data.

  1. 01

    Get bike ped sensor

    This capability provides the location, coverage, and data range for a specific bike or pedestrian count sensor.

  2. 02

    Get crash injuries

    Use this to get full details on every person involved in a specific collision using a collision ID.

  3. 03

    Get pothole work order

    This capability retrieves all street segments associated with a specific pothole work order via its defnum.

  4. 04

    List bike routes

    Access the city's protected and signed bike network segments, filtered by borough, street, or facility class.

Capability set02 / 02

05-08

4 capabilities in this set.

Part of 8 available through NYC Open Data.

  1. 05

    Search bike ped counts

    This capability pulls hourly or interval volumes for bike and pedestrian traffic from the NYC sensor network.

  2. 06

    Search pothole work orders

    Search through closed DOT pothole work orders to track street condition repairs.

  3. 07

    Search traffic crashes

    This capability searches NYC motor-vehicle crash reports using filters like borough, zip code, or date.

  4. 08

    Top crash factors

    Identify the most frequent primary contributing factors for crashes within a specific time window.

One connector, every AI

NYC Open Data works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put NYC Open Data to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 8 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of NYC Open Data, so you can see the experience inside your AI.

It does not authenticate your account with NYC Open Data. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

NYC Open Data Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_iZp5oUFU0SfRxe8rVjSXOxN03igtngcDMCs3KHpg/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — NYC Open Data capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "nyc-traffic-street-conditions-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_iZp5oUFU0SfRxe8rVjSXOxN03igtngcDMCs3KHpg/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? How to give Claude access to NYC Open Data

See all the AI clients this connector works with ↑

Who it's for

Built for the work NYC Open Data owners hand off.

This MCP is built for professionals who need to turn raw NYC municipal data into reports or analysis.

  • 01

    Urban Planners

    Use the agent to analyze mobility patterns and bike network coverage.

  • 02

    Data Journalists

    Hand off the heavy lifting of querying crash datasets and injury details to your AI.

  • 03

    Mobility Analysts

    Use sensor counts and crash factors to build safety and traffic models.

FAQ

Questions NYC Open Data owners ask.

  • 01

    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.

  • 02

    Can I see specific injury details for a crash?

    Yes. If you have a collision ID, you can use the capability to see the age, injury severity, and safety equipment used by people in that crash.

  • 03

    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.

  • 04

    What kind of sensor data is available?

    The MCP provides interval volumes for both bike and pedestrian traffic from the city's sensor network.

  • 05

    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.

  • 06

    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.

  • 07

    How current is the data?

    Each dataset is updated on its own cadence (311 daily, trip records yearly, tonnage monthly, ...). The get capabilities and search_datasets expose the last update timestamp, and the rows you read are the platform's current state.

  • 08

    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.

Connect NYC Open Data to Claude, Cursor, ChatGPT & more