Connect Nyc Events Permits 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 city event data and street closure info.

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

    Count events

    This capability provides a quick count of upcoming NYC permitted events within a specific timeframe. Use it to see how many results to expect before you pull a full list.

  2. 02

    List events

    This capability returns a list of upcoming NYC permitted events including names, dates, locations, and street closure types. You can filter by borough or event type, and use the closures_only flag to find only those events blocking streets or sidewalks.

  3. 03

    List summer sports

    This capability retrieves details for Parks Summer Sports & Entertainment and Kids in Motion sessions. It provides the borough, park name, date, and reported attendance for these seasonal programs.

  4. 04

    Search historical events

    This capability searches through nearly 2.9 million permitted events recorded since 2007. It uses the same filtering logic as the upcoming event capability to find past parades, festivals, or street events.

Capability set02 / 02

05-08

4 capabilities in this set.

Part of 8 available through NYC Open Data.

  1. 05

    Top event types

    This capability ranks upcoming event types by their frequency. It helps you identify which types of events are most common in your chosen window.

  2. 06

    Top historical event types

    This capability ranks historical event types by count. You can use it to compare the current event landscape against what happened in the past.

  3. 07

    Top summer sports

    This capability identifies the most frequent sports reported in summer sessions. It lists the most common activities like basketball, soccer, or pickleball.

  4. 08

    Top summer sports parks

    This capability ranks parks and playgrounds by the number of summer sports sessions they hosted. Use it to find the most active recreation areas in the city.

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_ZKvMPLoZN3F4RYRCm3lXWx5Ye6uhwqzGXxLapTjX/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-events-permits-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_ZKvMPLoZN3F4RYRCm3lXWx5Ye6uhwqzGXxLapTjX/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 designed for people navigating the logistics of New York City life and travel.

  • 01

    Trip Planners

    They use the capability to find local attractions and avoid street closures during their stay.

  • 02

    Logistics Coordinators

    They check historical event patterns and upcoming street closures to manage movement in the city.

  • 03

    Local Residents

    They use the summer sports and local event data to find community activities for themselves or their families.

FAQ

Questions NYC Open Data owners ask.

  • 01

    Do I need an API key to use this MCP?

    No, this MCP is keyless and works immediately once connected through Vinkius.

  • 02

    Can I find out if a street will be closed for an event?

    Yes, you can use the list_events capability with the closures_only flag to find events that cause full street, partial sidewalk, or curb lane closures.

  • 03

    How far into the future can I see upcoming events?

    The capability can look ahead up to 365 days, though some planned dates extend into 2027.

  • 04

    What kind of summer programs are included?

    The data includes Parks Summer Sports & Entertainment (S.S.E) and Kids in Motion (K.I.M.) sessions.

  • 05

    How much historical data is available?

    The capability provides access to approximately 2.9 million permitted events dating back to 2007.

  • 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

    Do the text filters ignore case or match partial values?

    No. The NYC data platform only supports exact-match filters, so a filter value must equal the stored value. In this MCP, event types are stored as "Sport - Youth", "Special Event", "Farmers Market", "Block Party", "Street Event", "Parade" and similar; boroughs as full names ("Manhattan", "Staten Island"); the permitting agencies as "Parks Department", "Street Activity Permit Office", "Police Department" and "Mayors Office of Media & Entertainment" (the entertainment agency is stored with a straight apostrophe); street closures as "N/A", "Full Street Closure", "Partial Sidewalk Closure" or "Curb Lane Only". Use top_event_types, or a list capability with no filters, to see the exact stored values before filtering.

  • 08

    Why do the upcoming-event capabilities use a forward window?

    The current permitted-events table holds about 31,000 rows and carries future planned dates (into 2027), so list_events and the type rankings scan a forward window from today (default 90 days, max 365). The historical table holds about 2.9 million rows, so its capabilities scan a lookback window instead (default 90 days, max 365, capped at today). Both windows keep every query under a second.

  • 09

    Why does list_summer_sports return few or no rows in autumn?

    The Parks summer sports and Kids in Motion programs run seasonally, roughly April to mid-July. The 2026 season data ends at 2026-07-17, so a lookback window starting in autumn holds few or no sessions. Use days: "365" to reach back into the last full season. Most sessions also leave the sport unspecified, so the top_sports ranking starts with an "Unspecified" row.

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