Download PDFMarkdown Version

Connect Nyc Flooding Floodnet to ChatGPT, Claude and Gemini

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 flooding data and sensor details.

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 · 5 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-03

3 capabilities in this set.

Part of 5 available through NYC Open Data.

  1. 01

    Flood events by sensor

    This capability retrieves all recorded flooding events for a specific sensor ID. It also returns the total event count and the deepest flood recorded at that location.

  2. 02

    List flood sensors

    Use this to get a list of the approximately 500 installed FloodNet sensors. You can filter the results by borough, NTA, or ZIP code.

  3. 03

    Lookup flood sensor

    This capability pulls the full installation record for a specific sensor ID. It provides the street name, borough, coordinates, and tidal influence data.

Capability set02 / 02

04-05

2 capabilities in this set.

Part of 5 available through NYC Open Data.

  1. 04

    Search flood events

    This capability searches the historical database of street-flooding events since 2020. You can filter by sensor name or specific date ranges.

  2. 05

    Top flood sensors

    This capability identifies the most flood-prone locations by ranking sensors based on their recorded event counts.

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.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

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. 5 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_lwY5j736vnhWB1WVYBNjw4QlyHI7wYpsy3W1CK0T/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-flooding-floodnet-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_lwY5j736vnhWB1WVYBNjw4QlyHI7wYpsy3W1CK0T/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 handling urban resilience and environmental data.

  • 01

    Resilience Planners

    They use the data to identify high-risk zones for infrastructure upgrades.

  • 02

    Drainage Engineers

    They pull depth and duration metrics to model stormwater runoff.

  • 03

    Environmental Journalists

    They query specific sensor events to report on local flooding impacts.

FAQ

Questions NYC Open Data owners ask.

  • 01

    Do I need an API key to use this NYC flooding data?

    No. This MCP provides keyless access to the DEP FloodNet records.

  • 02

    What kind of flood data is available?

    You can access start and end times, maximum depths in inches, and the duration water stays above 4, 12, and 24 inches.

  • 03

    How many sensors are in the network?

    There are approximately 500 installed sensors across New York City.

  • 04

    How far back does the flooding data go?

    The recorded street-flooding events in this dataset go back to 2020.

  • 05

    Can I filter sensors by location?

    Yes, you can filter the sensor list by borough, NTA, or ZIP 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 many FloodNet sensors are installed?

    About 500 sensors are installed citywide and the table of flood events has a few thousand rows recorded since November 2020. list_flood_sensors shows the installed sensors and their IDs; top_flood_sensors ranks them by event count.

  • 08

    What does a FloodNet sensor ID look like?

    Sensor IDs are slugs of the form "BK-richardson-st-n-11th-st-1x59w1" (borough letter, street intersection and a random suffix). lookup_flood_sensor and flood_events_by_sensor take the full slug; list_flood_sensors shows the installed IDs alongside the human-readable sensor names.

Explore

More in Climate

Suggestions

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